SharePoint Installer - Advanced Installer Community
coverride
Posts: 2
Joined: Tue Apr 30, 2013 1:50 pm

SharePoint Installer

Hi all, this is my first post.

I'm trying to create a SharePoint installer for SP2010 and having issues related to deploying wsp files.

I'm currently using AI 10.0 Enterprise.

I've attached a test wsp, an aip file and a visual studio 2010 solution used to create the WSP, here's what I've done in AI.

-Create new Enterprise Project
-In the left pane, select SharePoint
-Right click WSP Files folder and selected "Add WSP file"
-Choose TestProject.wsp
-On the Options tab for TestProject.wsp, select "Allow GAC Deployment", "Overwrite files created by other solutions", "Deploy globally", Deploy immediately"

When running the installer, everything seems to work just fine, but when I check Central Admin, the solution is added but it is not Deployed.

You'll notice that the wsp file contains a dll, a XML file deployed to the ISAPI directory and a Web Part. If I remove the Web Part from the VS 2010 solution and only leave the xml file and dll, the installer works perfectly. (wsp is added and deployed globally).

What is going on here? It seems fairly useless to have an installer that can deploy simple SharePoint files but not Web Parts.

Please help!

~Michael
Attachments
SharePointInstallerTest.zip
(57.67 KiB) Downloaded 251 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: SharePoint Installer

Hello Michael and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer and I apologize for my delayed answer.

Can you please enable the "Deploy to all nonadministrative virtual servers in farm" deployment target option for your WSP file and see if the behavior still persist?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
coverride
Posts: 2
Joined: Tue Apr 30, 2013 1:50 pm

Re: SharePoint Installer

Daniel,

This change did in fact fix my issue. Unfortunately, this isn't a very clean solution. For people who want the .wsp file installed only on a specific web application I could see this being a problem. For my situation it is fine.

The following command lines should be what is run when a solution is deployed globally:

Add-SPSolution mysolution.wsp
Install-SPSolution -Identity mysolution.wsp -GACDeployment -WebApplication http://somesite

In my situation, http://somesite is using a host header ("somesite") but the site is named "site" in IIS. When the option "Select target websites during install" is chosen, the site name in IIS seems to be what is displayed in the website selection dialog. If the site name is passed to the Install-SPSolution CmdLet instead of the hostheader, the cmd will fail.

Thanks.

Return to “Common Problems”