Hi, I have a VS2005 feature project, I can deploy the feature without problem using VS2005 but I need to integrate the feature project in an msi to be deployed automatically with my msi setup project
Thanks
packaging a feature project in an msi setup project
Hot Topic
- Design processes for commutability?? MCSD.NET Book
- Interfaces vs overloaded methods
- SOA - Transaction/compensation/cordination
- Extending a web application for Internet employees?
- Creating Visio Diagrams in an ASP.Net Web Form Programmatically (C#)
- how to quote content
- basic question 3-tier
- Changing the Task Form depending on the user opening it
- To use DevForce O/RM or Datasets?
- MOSS 2007 installation on a Domain Controller
SharePoint Products
- How do i get my web part to remember input when it reloads ???
- Question about UI layer
- How to Read and Update User Profile
- Best practice using data types in data access layer?
- What is the scope of static webservice object
- About Report center site
- Connecting MOSS2007 to Office 2007
- Cannot access Sharepoint Services site
- Calling Biztalk Rules Engine Remotely
- show a progress bar while web part is loading..
packaging a feature project in an msi setup project
Dasa
Thanks for the links I will investigate and experiment into this!
Lucy
asalcedo
Hi I want to do exactly the same thing. Did you find any suitable articles or anything helpful
Lucy
Hosma293
Sorry I'm still new to SharePoint and visual studio. Whats a WSP and how do I do that So far I have used the SetUp wizard project and have implemented the System.Configuration.Install Installer methods.
Lucy
alphonso
Hi Lucy,
If u want to learn how does solutions works, u can see my blog post here > http://blogs.coforcert.com/dntamack/Lists/Billets/Post.aspx ID=28
and u can get the article about solutions here > http://blogs.coforcert.com
Best regards
remedios_
The way I'd do it is to have the feature be part of a WSP, then have the msi deploy the wsp...
Fluxtah
A WSP (WSS Solution Package) is essentially a type of CAB file. It's built using the SharePoint Solution Framework and is a kind of installer for Features and template files into moss. By deploying a wsp using stsadm, moss takes care of all the overhead of provisioning the files to their correct location (layouts, 1033, wpresources, etc)
There are tools out there which help in the creation of WSPs, some of which can be integrated into Visual Studio. They should take most of the guesswork out of creating the WSP.
WSPBuilder
WSP Project Template for Visual Studio (I'm partial to this one
)
WSSv3 Reference on Solutions from MSDN
-Rich