Determining project and file types in preexisting code

[jeffc]

I'm maintaining some older code, apparently created in Vis Studio 2003. I
have Vis Studio 2005. When I open this solution, it says it has to convert
all the projects. There are some problems with the application and what I'm
trying to do is recreate the original application from scratch in 2005, and
then copying the code over. It's not clear how to reverse engineer this.
For example, when I add a new item to a project, you can choose from
templates like Component Class, Installer Class, and Windows Service. Each
of these has the same icon. So how do I know by looking at the original
project which of these types the file is? Or does it matter? Also, these
files have a nested .resx file. But when I create one of those file types
in a new project, say File1.cs, it nests a file called File1.Designer.cs.
How do you reconcile this with what was in the original project? thanks for
any help

 

[Otis Mukinfus]

I'm maintaining some older code, apparently created in Vis Studio 2003. I
have Vis Studio 2005. When I open this solution, it says it has to convert
all the projects. There are some problems with the application and what I'm
trying to do is recreate the original application from scratch in 2005, and
then copying the code over. It's not clear how to reverse engineer this.
For example, when I add a new item to a project, you can choose from
templates like Component Class, Installer Class, and Windows Service. Each
of these has the same icon. So how do I know by looking at the original
project which of these types the file is? Or does it matter? Also, these
files have a nested .resx file. But when I create one of those file types
in a new project, say File1.cs, it nests a file called File1.Designer.cs.
How do you reconcile this with what was in the original project? thanks for
any help

Seems like a lot of work to retype all the code from the original application.

If I were doing it I would let VS 2005 update the projects (you can specify
making a backup during conversion) and then correct the bad areas in the new
projects.

VS 2k5 does a pretty good job of conversion unless there are some really quirky
things in the original code.

Good luck with your project,

Otis Mukinfus
http://www.arltex.com
http://www.tomchilders.com

 

[jeffc]

Seems like a lot of work to retype all the code from the original
application.

If I were doing it I would let VS 2005 update the projects (you can
specify
making a backup during conversion) and then correct the bad areas in the
new
projects.

VS 2k5 does a pretty good job of conversion unless there are some really
quirky
things in the original code.

There might or might not be quirky things. In any case, it is what we are
doing to try to eliminate some problems. Any help on the OP appreciated.