Tag Info

New answers tagged

1

If you created the Site template before the Applying the English Language pack then it should be a problem. Because when you save the site as template it bundle everything which is part of sites and at that time English was not present so no reference for English.I am sure you getting some mismatch error. easy test is create a new template and try it


0

It is failing because you are deploying the lookup field before the lookup list. The relevant quote from the blog you referenced states: The trick to doing this right is understanding that the order in which the package deploys the artifacts is important. Look inside your feature designer, and I bet the element that provisions the lookup field occurs ...


1

Bin directory A partial trust location. By default, code that runs from this directory has a low level of code access security (CAS) permissions. Administrator must explicitly raise permissions granted to a Web Part so it can function properly. Because of this level of control and defense-in-depth, administrators tend to prefer that ...


0

1) be carefull with using "web application" to name a custom (Visual Studio) solution. A web application in SharePoint had a different meaning. Very rough. you link a domain to a web application. A web application contains all your site collections for that domain.(very rough it does a bunch of other stuff as well). You can create a new web application in ...


0

In my environment the site collection/web application parts are created by clicking. This is because you need to do it very rarely. Maybe you do it by powershell, there's no difference. Developing is done by visual studio. And yes there is a possibility to place a webpart on a page by code: http://www.stefangordon.com/add-web-part-to-page-programmatically/ ...


1

1) creating web application is full of clicking, being a sharepoint developer somtimes well for me most of the time incorporates sharepoint administration to it. You would use central admin to create web application and then site collection, or use powershell. web application central admin -> application managment -> click on manage web applications -> ...


1

The workaround is as follows: Open up your SharePoint 2012 solution in Visual Studio 2012/2013 In the Solution Explorer (use View -> Solution Explorer if you don't see it) expand your solution and browse to the Package within your project Double click on the Package.package entry to open up the package editor Click on the Advanced Tab The Additional ...


1

as user19952 noted, run powershell as admin. Problem: Your running an admin level task, the user DEVRSG\svcwss your user doesn't have the sufficient levels to run the dll for Microsoft.SharePoint.Administration. solution: click start -> click all programmes -> click Microsoft sharepoint 2013 products -> right click sharepoint 2013 management shell -> ...


1

A bit of detail. Performs a synchronization of the Windows SharePoint Services Solution Package (WSP) solutions stored in the configuration database with the files stored on disk. The .wsp files will be synchronized in the order in which they were submitted to the server. Reference This is same as Syncsolution in SP 2007. So bottom line, Synchronization ...



Top 50 recent answers are included