New answers tagged solution-deployment
This error happens if you deploy a solution which contains a visual web part to a different web application on the same farm as the web application where it is already installed. In other words, you have two web applications, A and B on the same SharePoint farm. You want to deploy solution S which contains a visual web part to web application B, but it is ...
It sounds like permission problem. Please verify few points: Make sure VS2010 is running as Administrator Make sure you are the local admin and having owner rights in SQL content DB. Also check your permission in few local groups
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 ...
Get new assemblies. If you cannot deploy dependent assemblies to the GAC, then you will forever be struggling to update SharePoint's various config files with entries required to direct the fusion loader to the correct place. And, once you do that, you will not be supported.
Although not a good practice in Software Development, in this case you can create a Batch file with simple DOS Commands. You can run this batch file post Build/Deploy every time of the project using Visual Studio. In Batch file you can create folders and copy the files to specific paths you have hard coded in you project. Commands you can include: MD // ...
Top 50 recent answers are included