Search Results

to add files to the SharePoint root you have to include the files in your WSP and then in the solution manifest add the following elements: <RootFiles> <RootFile Location='CONFIG\my_file.xml' /> …

I think you are referring to the case when you have a Visual studio solution containing multiple projects. Deploy solution deploys all projects (WSP files) and Deploy just deploys the current project. …

I do recommend you to take a look at Gary "PowerShell" Lapointes solution deployment script: http://blog.falchionconsulting.com/index.php/2011/04/deploying-sharepoint-2010-solution-package-using-powershell-revisited …

It could be the (in)famous loopback adapter issue. Disable it on your demo machine, reboot and try again. (That is if you're developing on the same machine that is hosting your web apps) Read more he …

Try to uninstall the feature using Uninstall-SPFeature <Guid> -Force, where GUID is the guid that you get from the Get-SPFeature cmdlet.

For Web Parts your feature must use the Site scope. The Web Part Gallery only exists on the Site Collection level.

Corrected - does not answer the question Create a root folder in your project and name it "80". All files in that folder will deployed to the wwwroot. . If you would like to add a .dll to the wwwro …

You need to enable the "SharePoint Server Enterprise Site Collection features" Site Collection feature. And Office Web Apps is not Excel Services. In Office Web Apps (is OWA the correct acroynom?) yo …

Yes you can use WSPBuilder to package all your stuff. It's a great tool for that. You should leave the site backup out of though and restore that manually. Regarding your error; make sure that you ha …

If you will deploy it several times the general recommendation is to use the declarative approach and create a list definition, this also allows users to create an instance of your list as normal.

Web Parts must be deployed to the Site Collection (Scope=Site) When using stsadm operation deploysolution you need to specify the site collection (or use -allcontenturls) Only run the stsadm commands …

The benefit of the Hub is exactly what you are describing. It's a HUB where you deploy and manage all of your enterprise content types. Other Site collections subscribe to the content types from the h …

The Local parameter can be used, and exists, for two reasons as you and Anders describes. 1) Execute the deployment immediatley withouth the timer service - on single server farms. …

I would recommend NOT to store appsettings in the web.config - use any other methods. SPWebConfigModifications are not reliable in all scenarions (just Bingle it and you'll find a plethora of posts ab …