Change/Rename Reusable SharePoint workflow template title

When saving a template of SharePoint designer workflow, it creates a pretty ugly title including the site it was created and all. I wanted to change this title to make it standard as our other feature naming conventions:

For tools related to repackaging the wsp file, please see my earlier article Here.

1. Copied the "SiteApprovalWorkflow.wsp" to C:\mywork\workbench
2. Extracted the WSP file using 7-zip > content extracted to "C:\mywork\workbench\SiteApprovalWorkflow"
3. Opened the file "C:\mywork\workbench\SiteApprovalWorkflow\Site Approval WorkflowListInstances\Feature.xml" and edited the Title="Workflow template "Site Approval Workflow" from web template "Channel Home"" to Title="Readify.Pwcs.Collabration.TeamSiteApprovalWorkflow", save the file.
4. Copied the file "makeddf.exe" to "C:\mywork\workbench"
5. Opened a command prompt @C:\mywork\workbench>
6. Executed the command – makeddf /p SiteApprovalWorkflow /d SiteApprovalWorkflow.ddf /c SiteApprovalWorkflow.cab

MakeDDF 1.0.1 (r119) · http://www.Stum.de
_________________________________________
CAB Filename: SiteApprovalWorkflow.cab
Base Path: SiteApprovalWorkflow\
DDF File Name: C:\mywork\workbench\SiteApprovalWorkflow.ddf
Using Absolute Path names: no

Finished execution on 2015-03-12 12:08:51

MakeDDF 1.0.1 (r119) · http://www.Stum.de
_________________________________________
CAB Filename: SiteApprovalWorkflow.cab
Base Path: SiteApprovalWorkflow\
DDF File Name: C:\mywork\workbench\SiteApprovalWorkflow.ddf
Using Absolute Path names: no

Finished execution on 2015-03-12 12:08:51

7. Copy the newly created file "C:\mywork\workbench\SiteApprovalWorkflow.ddf" into "C:\mywork\workbench\SiteApprovalWorkflow" folder
8. cd C:\mywork\workbench\SiteApprovalWorkflow
9. makecab /f "SiteApprovalWorkflow.ddf"
10. file gets created at: "C:\mywork\workbench\SiteApprovalWorkflow.cab"
11. Rename that to .WSP

What Each Product Backlog Item (PBI) State Means to You.

New – These are PBIs that someone has added to the product backlog and have not been reviewed by the product owner and have not been agreed to build.

Approved – These are PBIs that the product owner has agreed with, edited and made sure they are understandable for the team. Once approved they are ready for the team to pick up in sprint planning.

Committed – A Scrum team has discussed the PBI in sprint planning, created some tasks and agreed to do build the PBI in the current sprint.

Done – In sprint review, the product owner inspects the work the team has done and if he/she agrees it meets the requirements and quality standards, then the item is moved to done.

Developer productivity–script to deploy an assembly quickly to Global Assembly Cache (GAC)

Very often we want to deploy the assembly to GAC and test our work, without having to follow a quick deployment process. here is a script which does the assembly deployment (uninstall the old one and install a new version).

$ProgamFiles_x86 = "$env:ProgramFiles (x86)"

#configure GacUtil environment
set-alias gacutil "$ProgamFiles_x86\Microsoft SDKs\Windows\v7.0A\bin\GacUtil.exe"

# un-install the old version of the assembly
Gacutil /u "DirectEnergy.OAM, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b6a416a3e4d1c768"

# Install new version of the assembly
Gacutil /i "C:\mywork\scm\DirectEnergy.OAM\Development\R1\DirectEnergy.OAM\bin\Debug\DirectEnergy.OAM.dll"
Also, you could create a shortcut in your desktop with the following attribute:
Target: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe "C:\mywork\ps\DirectEnergy.OAM\Deploy-DE_OAM_DLL.ps1"
Start In: C:\Windows\System32\WindowsPowerShell\v1.0

A .net disassembler/decompiler

Now that Red Gate have started charging for the .NET Reflector tool you might want to check out these free alternatives instead…

Telerik JustDecompile

JetBrains dotPeek

(Open Source) ILSpy

[

All can create Visual C# project. The generated code did not compile for JustDecompile and Reflector. In one case, ILSpy made a code that compiled (just references had to be set) The mistakes IlSpy did not look as complicated as one found in others. All generated code can be fixed if one know C# well enough.

An interesting direction can be used to decompile code using both JustDecompile and Ilspy and merge the codes that are correct because these decompilers (and third as well) seem to make different mistakes.

]