Discussion Locked

Changing .NET's core project templates

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us about situations in which you've found it necessary to change .NET's core project templates, as discussed in this week's .NET e-newsletter. Have you used this customization capability to implement architectural standards into the code templates? Tell us about your experiences.

1 reply

by mattohare

In the old Access 1/2 days, I use to change the things that came with MS-Access.

I ran into problems though. First, I found that I needed the old process back for some new task that I did. Second, I found I'd loose my changes when I had to reinstall access from some file corruption problem.

So, now, where I can, I make copies and change my copies. Even to the point of not putting my own changes in my MS-Word's normal.dot. My work seems to survive longer.

However, it's a great point to have some uniform starting point for the projects that we really do, instead of what MS thinks we'll do.

This discussion is closed to new replies.