Speed Up with Project Templates Using Visual Studio 2005

Print Add To Favorites Email To Friend Rate This Article
Speed Up with Project Templates Using Visual Studio 2005 - Part 3

page 6 of 10

by Ameet Phadnis
Feedback

Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 38368/ 65

Article Contents:

Signing the Assembly

In Visual Studio 2005, signing assembly is easy. Steps involved are:

· In Solution Explorer, from the Project Menu, Click Properties.

· In the Project Designer click the Signing Tab.

· Select the Sign the Assembly check box.

· In the Choose a strong name key file dropdown list select New…

· The new key file will be stored as .pfx format.

· In the create Strong Name Key dialog box enter a name and password for the new key file.

Figure 3

· Click Ok.

· Your signing tab should now look like the following.

Figure 4

· You can also browse to an existing key file if you have already created one.

« (Page 5)

View Entire Article

(Page 7) »

User Comments

Title: Clarification
Name: Jon
Date: 2007-01-09 3:34:33 PM
Comment:
As a clarification, VS will still use the old version even after I go into the cache through the control panel and remove it.

Title: Development Process
Name: Jon
Date: 2007-01-09 3:32:22 PM
Comment:
What's the best way to actually build and test a wizard from the ground up?

I have my build process for the Wizard's project set up to sign the DLL and automatically add itself to the GAC (using: "gacutil.exe /if $(TargetPath)").

The problem is they will stay in the cache after every rebuild, so I need to either update the version number in the vsTemplate file and the project after each compile, or restart Visual Studio each time I want to test a new build.

Advice?

Title: VB Bug ?
Name: frisla
Date: 2006-09-20 9:52:51 AM
Comment:
Hi A

The test for C# and VB.NET wore created as separated projects - C# Custom wizard and template project, VB Custom wizard and template project.

In VB as soon as I try to access my IWizard implementation, my VB template project wil not unfold, hence the error message. The template itself executes perfectly, but again as soon as I try to reference my custom wizard, using an "WizardExtension" entry in the xx.vstemplate I get the error message.

Any suggestions

- Thanks -

Title: No
Name: Ameet
Date: 2006-09-19 7:37:26 PM
Comment:
The article was written using VB.NET and not C#.NET.

Check whether you have created the template itself for C#.NET...

Title: VB Bug ?
Name: frisla
Date: 2006-09-19 4:01:54 PM
Comment:
Why is it you get a, "Unable to copy the file 'Application.myapp' from the project template to the project. Cannot find file ...." failure when you use VB.NET (2005), but using C# is a walk in the park ??????

Is the execution of the IWizard interface different in VB.NET ?????

Product Spotlight