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: 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

Reply via email to