+1 for WSPBuilder - Having worked extensively with workflow deployment recently, this was a saviour
From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Jeremy Thake Sent: Wednesday, 6 May 2009 2:45 PM To: ozmoss@ozmoss.com Subject: RE: Multiple workflows per VS project If that is the case have you looked at WSPBuilder or STSDev as an alternative? Didn't realise that was an issue, have added it to the list http://www.sharepointdevwiki.com/display/public/Solution+package+development +tool+comparisons From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Turner Sent: Wednesday, 6 May 2009 12:40 PM To: ozmoss@ozmoss.com Subject: RE: Multiple workflows per VS project WSP view will be blank. The extensions won't/can't package workflows into WSP's. I normally run a post build step and include a solution.xml and ddf file. It is meant to be fixed in VS2010 (I logged in on Connect a while ago). Regards Paul Turner Senior Solution Specialist M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966 A: 66 Henley Beach Road, Mile End SA 5031 E: paul.tur...@sdm.com.au W: www.dws.com.au <http://www.dws.com.au/> _____ From: ozmoss@ozmoss.com [ozm...@ozmoss.com] On Behalf Of Chris Milne [chris.mi...@dataaspects.com.au] Sent: Wednesday, 6 May 2009 12:27 PM To: ozmoss@ozmoss.com Subject: RE: Multiple workflows per VS project Thanks M, When I mentioned that workflow.xml has no delete/rename, I was talking about Solution View. Actually, my WSP view is completely empty. I thought it was some kind of fault but then I wasn't sure if workflows were packaged that way; so they definitely are? I have no files listed in the WSP view.. I read somewhere you need to do a release build to build the WSP first, which I've done, but no dice, nada. Sorry, not sure what you mean you say pkg folder - this is in the Solution Explorer? Thanks for your help. C From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Matthew Cosier Sent: Wednesday, 6 May 2009 12:46 PM To: ozmoss@ozmoss.com Subject: Re: Multiple workflows per VS project Sounds like you're trying to edit it within the WSP view. Click the 'Show hidden files' button in VS, then include the pkg folder into your project (this is the one it generates). You should be able to add to/manipulate this, then go into your WSP view and hit the refresh button - play around with it. M On Wed, May 6, 2009 at 12:23 PM, Chris Milne <chris.mi...@dataaspects.com.au> wrote: Hey guys, I'm creating a workflow solution using VSeWSS 1.3. I have 3 sequential workflows to create which I was expecting to add to the same project, deploy as a single assembly in a feature and away I go. However, the VSeWSS Sequential Workflow template comes with a feature.xml and workflow.xml, and the workflow.xml relates to the existing workflow. If I add new workflows to the project, it doesn't create a workflow.xml for each one, so I can create new ones manually, each named the same as the workflows(.xml), but VS doesn't let you rename the original workflow.xml (right-click, no rename/delete). My additional element manifests don't seem to be included in the deploy either, resulting in a file not found error. This kind of suggests that you're supposed to leave it as is, even though you can change the element manifest filename reference in feature.xml. Would I have to create one project per workflow? Then I'd have 3 different features to activate in the portal, when really they're all part of the same solution. Thoughts/Ideas? Kind regards, Chris _____ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: <http://www.codify.com/lists/ozmoss> http://www.codify.com/lists/ozmoss Other lists you might want to join: <http://www.codify.com/lists> http://www.codify.com/lists _____ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: <http://www.codify.com/lists/ozmoss> http://www.codify.com/lists/ozmoss Other lists you might want to join: <http://www.codify.com/lists> http://www.codify.com/lists _____ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: <http://www.codify.com/lists/ozmoss> http://www.codify.com/lists/ozmoss Other lists you might want to join: <http://www.codify.com/lists> http://www.codify.com/lists _____ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: <http://www.codify.com/lists/ozmoss> http://www.codify.com/lists/ozmoss Other lists you might want to join: <http://www.codify.com/lists> http://www.codify.com/lists _____ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: <http://www.codify.com/lists/ozmoss> http://www.codify.com/lists/ozmoss Other lists you might want to join: <http://www.codify.com/lists> http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
