I have a solution with a custom solution target (x86). When I create a new project (.net 2.0 Windows Forms Application), it creates the project file, but only with the 'Any CPU' project target. The problem here is that if I press F5 to run the app, it doesn't build first (presumably because there is no 'Any CPU' target), which is a pain. To fix this, I have been going into the configuration manager, finding the new project, and adding a new project target of x86 and clicking the build checkbox. After that, the project works as expected, building before running on F5 and so-on.
The question - is there a way to automatically have newly created projects with the existing solution targets?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hello packratt_jk,
I must have a lesser version of VS to yours, as I do not even know (or find) where to set the project target.
But, this idea might help.
Once you have changed the project setting as you describe, can you go File -> Export Template, and create a new template with your settings?
You can then choose this template when you next create a new project.
Regards,
Dabas
Dabas,
Thank you for your response. The Project target can be found by viewing the project properties, Build tab, Labeled 'Platform'.
I think your approach of using a template is a good idea though - it will resolve this issue as well as keep future projects consistent. I have made a new project and exported it as a template, then created a new project from this template. Most of it works great, but there are a few things I would like to alter that I was hoping can be done in the template itself:
1) I would like the .cs filenames to have a name matching the project. For example, if I have a project TestApp, than I would like to have file named TestApp.cs, not Template.cs as per the template.
2) I would like the namespace / class names to match as well. Looking in the template file, I see that there is a '$safeprojectname$' variable (used in AssemblyInfo.cs). I have tried to alter the .cs files to use this variable instead of the hard-coded names, but when I re-zip the files they are no longer detected by VS. Also, if i extract the files with WinZip (v 12.0-8252), I get a CRC error. I am assuming that VS does some non-standard things with the .zip file, and that's why when I re-zip it with winzip VS no longer recognizes it - is there a tool in VS that I should be using instead to re-zip the files?
The project I made I named BoilerPlate. The template I created from the project I named BoilerPlate as well. After the template was made, I extracted the files and altered them so that the text BoilerPlate would be replaced by the new project name ($safeprojectname$). After that, I re-zipped the files and copied that zip to the templates directory. So now, when I make a new project based on that template, the namespace and project name are set to the new project's name (this is the desired behavior). The only thing that I can't seem to change is the actual file names themselves. For example, if i create a new project named NewProject based on this template, I will get a NewProject.csproj, as well as the files from the template (BoilerPlate.cs, etc). Inside the BoilerPlate.cs file, there is a namespace declaration of NewProject, as well as a class named NewProject (this is the desired behavior). This behavior resolves my initial question, as it does also pull in the project build targets and other project settings (references, etc) in from the template. The last remaining problem (albeit a small one), is that the I would like the file BoillerPlate.cs to get created and added to the project as NewProject.cs. This is a simple rename operation, but automating it would be nice. I've read msdn's documentation, and there doesn't seem to be any support for this in templates (they just splat down the files from the zip), but I thought maybe somebody might know of a loophole in the mechanism.
The solution is not necessarily a time saver, but one I use myself.
You just create two templates:
The project template, with no files in it. Includes your .csproj file only
An item template, which includes your .cs file
Once you have loaded the Project from your project template, you click on Add, New Item, and at the bottom, under templates, you will find your BoilerPlate template, which you can then rename at will.
Business Accounts
Answer for Membership
by: packratt_jkPosted on 2008-11-07 at 10:07:57ID: 22907038
Really? 25 hours and not even a comment?