Tag Info

New answers tagged

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

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.


0

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 // ...


0

You have set the scope of the feature to site level so you don't need the -WebApplication. Solutions with no WebApplication scoped features will be deployed globally this is the normal behavior. The Enable-SPFeature cmdlet is what you would use to activate the feature at the site collection level by specifying the -Url parameter. Check out MSDN - Elements ...


0

Go to the Manifest.xml and add the AlwaysForceInstall="TRUE" to it. This will allow you to deploy your solution now.


1

For 60 Users and apps you are mentioned, I think one server farm is enough.If you dont have future expansion and adding more services in it. I would go with One WFE/App Server and One Database server, this is good for upto 10K as per MSFT guideline. Please check this PDF will give you more idea. But still if you want to use 3 server farm, then All web ...


0

After much beating of head and hours of Support time from MS, we determined that the Config Refresh and Timer Job Refresh jobs were missing from the affected server. The solution, therefore was to remove the server from the farm and rejoin it. Once we did that, the solution package deployed without any further issues.



Top 50 recent answers are included