Tag Info

New answers tagged

1

The first icon is Results to File. The result of some action, bundling sounds logical in this context. The Second icon is Style sheet (css) that it is a stylesheet file. Visual studio icon download


0

You get these files as a result of bundling and minification process in Visual Studio. In other words, bundling lead to fewer HTTP requests, resulting in faster response times. Check out web essentials, which can be used as VS add-on to facilitate bundling: http://vswebessentials.com/features/bundling


2

SharePoint solutions (non-sandboxed) can be deployed at both two scopes "Globally" and "Web Application". As stated by bloger Jan Steenbeek at Deploying solutions to a specific Web Application: "SharePoint has the annoying" (Debatably) "habit of forcing you to deploy globally whenever possible. When you try to deploy a global solution to a specific url ...


1

Short answer: a WSP cannot be deployed on a given Web app. First of all, a WSP can contain different artefacts: _layousts files (application pages, JavaScript, CSS, images...): those "resources" are by definition available to all the SharePoint farm. Features Features that embed a Web part or anything else that requires a web.config modification. In ...


2

Here is the powershell command to deploy WSP to particular web application only : Install-SPSolution your_solution_name.wsp –webapplication http://server1:123 –GACDeployment


0

You should consider the following during the move: You may only need WSP which contains timer job logic that can be deployed to 2010 platform. You have to perform IISReset and restart timer job service to have full impact in 2010 version. If you want to improve the timer job for 2010 (for whatever reasons) source code must be kept alive and you should be ...


0

You should configure a build server for your TFS, and set up your SharePoint solution in Visual Studio to use this build server for automated builds. As starting point you can use these posts here and here, and the CodePlex project here.


0

If you get an error adding SharePoint DLL which states Could not load file or assembly 'microsoft.sharepoint, Version=12.0.0.0 you can try using this script instead [Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") and you can continue exporting the WSP from your 2007 environment $farm = ...


0

The WSP name for a solution is defined within the Package\Package.package file of the solution as the “name” property inside the element. You need to open the code/project using Visual Studio, go to the Package file and then change the "name" attribute value to the desired modified name, and rebuild it. VS2010: Changing the SharePoint wsp file name


0

Open The Package.Package file and change then Name attribute. Example <package xmlns:dm0="http://schemas.microsoft.com/VisualStudio/2008/DslTools/Core" dslVersion="1.0.0.0" Id="d3150724-5644-479c-99f3-fc99af5bfdc6" solutionId="d3150724-5644-479c-99f3-fc99af5bfdc6" resetWebServer="true" sharePointProductVersion="15.0" name="NEWNAME" ...


0

You can use MSBuild to build the packages (particularly helpful if you want to automate the build process as part of TFS) https://msdn.microsoft.com/en-us/library/ee231588.aspx or use a plugin like CKSDev for Visual Studio (which i personally use) to give you an option to build packages from the IDE itself. ...



Top 50 recent answers are included