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 you'll probably end up editing what the builders give you for some requirements anyway - unpack some CABs and have a look at what they contain.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Noone Sent: Friday, 28 November 2008 12:46 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: VS Project type for feature - a few questions 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 feature - a few questions 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" xmlns="http://schemas.microsoft.com/sharepoint/"; > <!--TEMPLATE files--> <TemplateFiles> <TemplateFile Location="IMAGES\HelloWorld\AfricanPith32.gif" /> </TemplateFiles> </Solution> STSDEV is very useful in terms of building sharepoint solution, http://msdn.microsoft.com/en-us/magazine/cc337895.aspx Cheers Jeffery On Fri, Nov 28, 2008 at 1:38 PM, Caroline Specker (AU) <[EMAIL PROTECTED]> wrote: 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 install it by running the stsadm command addsolution (http://technet.microsoft.com/en-us/library/cc263162.aspx). You can run this on a server that has central admin on it. Because you are installing a solution it will automatically install each feature in the solution onto every web front end on the farm. When you create a feature you can set the scope for the feature to Web, Site, WebApplication or Farm. Look at this link to see what elements in a feature can be scoped at different levels: (http://msdn.microsoft.com/en-us/library/bb861828.aspx). A custom action can be scoped at any of these levels. Why do you want to copy the files manually when you can run a simple command line to do it properly for you? If you were to go down the path of installing individual features that were not wrapped up in a solution you would have to copy the files to their destination manually, and then run a command on each WFE to install the feature, but solutions remove that requirement. I believe that installing a solution will do an iis reset automatically for you. Sombody please correct me here if I am wrong. Other things you should know: Once you have installed the solution that means it is available in Central Admin. You still need to deploy the solution to sites. This effectively makes the features inside the solution available to the areas you deploy it do. You can deploy the solution either through stsadm deploysolution (http://technet.microsoft.com/en-us/library/cc262459.aspx), or from Central Admin>Operations>Solutions Management. Hope this helps. Caroline ________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Paul Noone [EMAIL PROTECTED] Sent: Friday, 28 November 2008 11:43 AM To: listserver@ozMOSS.com Subject: [OzMOSS] VS Project type for feature - a few questions Hi all, I finally have some developer questions! This is my first foray into creating a feature for MOSS so please be gentle. J I have created a custom list action and a 'copy item' command for the ECB and would now like to deploy them with a single feature. I now have the following files and folder structure: CopyDeleteAll.ListActions\12\TEMPLATE\FEATURES\CEOCopyDeleteAllListActio n\feature.xml CopyDeleteAll.ListActions\12\TEMPLATE\FEATURES\CEOCopyDeleteAllListActio n\actions.xml CEO.CopyDeleteAll.ListActions\12\TEMPLATE\LAYOUTS\myCustomPages\CopyList ItemECB.aspx CEO.CopyDeleteAll.ListActions\12\TEMPLATE\LAYOUTS\myCustomPages\DeleteAl lListAction.aspx So far so good. I would now like to wrap everything up in a solution but WSPBuilder Extensions expects a project file. So... Questions: - What type of project file should I start with for something like this? I have the VSeWSS for VS 2008 installed. - Do I install on the application server or (one of) the web front ends? - Can I set the scope to Site? - Is there anything preventing me from just copying the files to their destination manually? - Does this require an IIS reset? - Is there anything else I should know? Thanks in advance, Paul ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ************************************************************************ ****** - NOTICE FROM DIMENSION DATA AUSTRALIA This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. ************************************************************************ ****** ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
