VSTO Power tool: SharePoint Workflow package generator

Sharepoint Workflow package generator

STEFANO DEMILIANI — Tue, 04 Mar 2008 11:41:54 GMT

Sharepoint Workflow package generator

re: VSTO Power tool: SharePoint Workflow package generator

David Marshall — Wed, 02 Apr 2008 01:00:23 GMT

As weel as the workflow dll and feature files, can I use this tool to package all the artifacts of my workflow?

- TaskContent Feature Files

- ASP.NET Association, Initiation and Task forms

re: VSTO Power tool: SharePoint Workflow package generator

Nikhil Khandelwal — Wed, 02 Apr 2008 01:12:46 GMT

Hi David,

Anything that you reference as "ElementFile" in the workflow feature.xml will automatically be copied - so if you reference your asp.net form as an "elementfile" it should be packaged in the WSP. However, the tool does not support content type feature files to be deployed.

Hope this helps!

-Nikhil

re: VSTO Power tool: SharePoint Workflow package generator

Joseph — Thu, 10 Apr 2008 11:19:58 GMT

Hi Nikhil,

I have tried using the tool. i am having a problem when i use it to deploy on another server.

Ex.

1. I develop the solution in Server A.

2. I create the .wsp using the tool.

3. Copy all the files (manifest.xml, workflow1.wsp, package.ddf,setup.inf, setup.rpt) to Server B.

4. Deployed the solution.

5. After i deployed it and run it in Server B, it seems it is (still) pointing to Server A. How do i know?

a. I changed all the "GUID" in the project with the GUID in Server B, but it says " can't find the list in the web ... "

b. then i tried to deploy in Server A, it works.

do you know why?

it might be irrelevant with this blog entry. Sorry.

re: VSTO Power tool: SharePoint Workflow package generator

Nikhil Khandelwal — Tue, 15 Apr 2008 08:06:54 GMT

Joseph,

What do you mean by "it seems it is (still) pointing to Server A"? The WSP itself does not have reference to any server locations.

-Nikhil

re: VSTO Power tool: SharePoint Workflow package generator

Peter Lang — Fri, 25 Apr 2008 01:20:17 GMT

Nikhil, We're working on some Infopath based workflows using VS2008. In the MSDN tutorial steps written for VS2005, it has a step for using a "GUID Generator" off the Tools menu. In 2008, i cannot locate this functionality. Is it needed ? If so, where is it lcoated now?

thanks!

re: VSTO Power tool: SharePoint Workflow package generator

Tom Van Gaever — Fri, 23 May 2008 16:36:17 GMT

It seems like the path to the wsp generator is changed:

now they use:

C:\Program Files\Microsoft VSTO Power Tools 1.0\Workflow Package Generator

if you edit this the tool will succesfully build the wsp file..

thanks for this tool, nice work!

re: VSTO Power tool: SharePoint Workflow package generator

Cory — Thu, 19 Jun 2008 23:33:03 GMT

A welcome tool - good work.

One nice addition would be an optional refresh of the wsp - it appears that invoking the tool a second time re-guids (id's) the solution.

Thanks,

Cory

re: VSTO Power tool: SharePoint Workflow package generator

Nikhil Khandelwal — Tue, 24 Jun 2008 10:45:34 GMT

Hi Cory,

You can use the SolutionId attribute on the feature.xml to ensure that it does not re-generate the solutionID. SolutionID is docmented here: http://msdn.microsoft.com/en-us/library/ms436075.aspx

Hope this helps!

-Nilkhil

re: VSTO Power tool: SharePoint Workflow package generator

Oscar — Thu, 06 Nov 2008 12:03:30 GMT

To recover the "Create GUID" tool under the Tools menu, just do this:

1 - Go to Tools menu / External Tools...

2 - On title text put : Create GUID

3 - On command put the location of guidgen.exe

by default is located on: "C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\guidgen.exe"

4 - Click Ok.

Then you'll see that now you have a new submenu under Tools menu named "Create GUID" that opens the GUID generation tool.

Hope this help!!

Regards

re: VSTO Power tool: SharePoint Workflow package generator

Sam — Thu, 18 Dec 2008 10:25:30 GMT

Hi Nikhil

This is a great post by U.

but I want to know that

"How can I Package the Blank site with Lists,Workflow,EventHandlers ...etc ?"

so that whenever I deploy that wsp package to any server directly that site is started with workflows and lists.....

Thanx...

re: VSTO Power tool: SharePoint Workflow package generator

Nikhil Khandelwal — Thu, 18 Dec 2008 22:00:20 GMT

Unfortunately, in VS 2008 we have not gotten to the state of being able to do that. You should check out VSEWSS for that.

-Nikhil

re: VSTO Power tool: SharePoint Workflow package generator

Jonathan — Mon, 03 Aug 2009 15:45:32 GMT

So where is it getting the assembly? When I rebuild the solution it packages up the old assembly. Even after I add and remove the dll from the GAC it uses the old assembly. It takes about 15 minutes before I can get it to build with the new assembly. Is it pulling it from some GAC cache or from a SharePoint / IIS cache?

re: VSTO Power tool: SharePoint Workflow package generator

Nikhil Khandelwal — Mon, 03 Aug 2009 21:15:03 GMT

This is the order in which it will try to search for an assembly:

1. Look in the directory that is passed in for feature.xml/current directory

2. Look in the bin\Release folder relative to the feature.xml.

3. Look in the bin\Debug folder relative to the feature.xml

re: VSTO Power tool: SharePoint Workflow package generator

Syed Yahya — Fri, 11 Sep 2009 09:48:27 GMT

I have been developing sharepoint workflow for the past one year and have always used the traditional method to deploy workflows.

In combination with your SharePoint Workflow Package Generator and the SharePoint Solution Installer (http://sharepointinstaller.codeplex.com/) I have been able to deploy my workflows faster and easier.

I would like to thank you for sharing with us the solution.

Cheers!