-
MailEnable: You are not permitted to post to the list (listserver@ozMOSS.com).
This list may be password protected, or you may need to have previously
subscribed to
the list in order to post to it.
Hi Paul,
I will have to skip your first question about wsp builder, but i'm sure someone
else will answer that one for you.
As for the rest:
To clarify, a solution is a collection of features that you install onto a
SharePoint farm.
Once you have your solution file (eg whatever.wsp) you
You can add the instruction in manifest.xml that controls whether WSS will
run IISRESET on each front-end Web server after the output solution package
has been deployed, upgraded, or retracted.
sample manifest.xml
Solution
SolutionId=24F91DED-8BA7-4633-8BA0-4C9B2A4387D7
ResetWebServer=True
Thanks Jeffrey and Caroline.
So what do people recommend for solution generation? STSDEV or WSPBuilder.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffery Tsui
Sent: Friday, 28 November 2008 1:58 PM
To: listserver@ozmoss.com
Subject: Re: [OzMOSS] RE: VS Project type for
Hi Paul
VSeWSS doesn't have an exact template for Custom Actions.
You first create a Empty sharepoint project and then add a new Module template.
I have an example here. This example creates a custom action for a code behind
page in sharepoint.
I liked wspbuilder to start from (in VS 2005), but once you've got the
idea, it's just as easy (and more controllable as I've had stuff
released I didn't want) to edit the features, elements, onet, solution
ddf and manifest xml files yourself - none of the 3rd part or MS
solutions are perfect, so
WSPBuilder.
Sezai
On Fri, Nov 28, 2008 at 12:46 PM, Paul Noone
[EMAIL PROTECTED] wrote:
Thanks Jeffrey and Caroline.
So what do people recommend for solution generation? STSDEV or WSPBuilder.
*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf
Of *Jeffery Tsui
*Sent:*