Advice needed: Packaging WSS-solutions
- From: fgunne@xxxxxxxxx
- Date: Wed, 07 Nov 2007 08:40:56 -0800
Hi!
We are building a "shrink-wrapped" WSS-solution for our customers.
I am currently looking into how we shall package the solution, and I
need advice on how this shall be accomplished.
The goal is that with minimal manual adjustments, the install shall
* Create a WSS-application, with our "skins" (colors, images, etc)
* Populate a site-collection with a pre-defined structure of sites.
Sites like "Admin page", "Reports", "Security" etc, where each site
has a certain layout, webparts, lists, etc
* Install a number of templates, webparts, etc for future
customization by us or the customer.
* Changes to underlying templates, etc are reflected in the populated
sites.
I am not new to WSS or web-parts development, but there seems to be a
few options on the best way to package our solution. Please note that
we don't want to go too far the "Sharepoint Designer"-way, where we
sit down and "design" the product at customer site.
Any advice on how-tos, tools, process, etc highly appreciated!
Thanks!
/Fredrik
.
- Follow-Ups:
- Re: Advice needed: Packaging WSS-solutions
- From: Daniel Bugday
- Re: Advice needed: Packaging WSS-solutions
- Prev by Date: Re: WSS 3.0 search and .DOCX files
- Next by Date: Re: InfoPath and WSS 3.0
- Previous by thread: InfoPath and WSS 3.0
- Next by thread: Re: Advice needed: Packaging WSS-solutions
- Index(es):
Relevant Pages
|