470,596 Members | 1,386 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,596 developers. It's quick & easy.

VS2005: Port project or recreate from ground up?

In C++, there is a compelling reason to recreate projects for the
VS2005 compiler rather than simply copy and recompile older code
(reason being C++/CLI syntax).

I'm wondering if there is any reason to do the same with C# code.
Does a newly created project have any differences in compiler switches
when compared to a ported VS2003 project?

Nov 17 '05 #1
3 1255
> In C++, there is a compelling reason to recreate projects for the
VS2005 compiler rather than simply copy and recompile older code
(reason being C++/CLI syntax).

I'm wondering if there is any reason to do the same with C# code.
Does a newly created project have any differences in compiler switches
when compared to a ported VS2003 project?

It depends, if you C++ was unmanaged only and have no support and uses MFC
extensively then recreating the project could be a wise choice, since the
..NET framework will reduce your code dramatically if you dump MFC.

For C#, VS 2002 and 2003 created it as .NET framework from the beginning,
there is no need to recreate the project since it is near identical. You
might want to remove self made code that is now part of the .NET framework,
like the serial port.
Nov 17 '05 #2
On Tue, 25 Oct 2005 12:28:39 +0200, "Olaf Baeyens"
<ol**********@skyscan.be> wrote:
I'm wondering if there is any reason to do the same with C# code.
Does a newly created project have any differences in compiler switches
when compared to a ported VS2003 project?
For C#, VS 2002 and 2003 created it as .NET framework from the beginning,
there is no need to recreate the project since it is near identical. You
might want to remove self made code that is now part of the .NET framework,
like the serial port.


Yes, I was talking about porting VS2003 projects to VS2005. I was
considering that dialogs are now split into two modules using partial
classes. That eliminates a lot of the "Compiler-generated, Don't
touch this" blocks within the code you're editing.

Of course if there is a tool that will convert the older format files,
that would be great. Some of my VS2003 dialogs are complex, and I'm
not looking forward to recreating them. I guess I could study the
newer output format and try to duplicate it, but that may be
time-consuming as well.

That kinda stuff...

Nov 17 '05 #3
On Wed, 26 Oct 2005 01:53:18 -0400, -DG- <-D**@nospam.com> wrote:
Re Chaning VS2003 dialogs, etc to VS2005 format:
I was talking about porting VS2003 projects to VS2005. I was
considering that dialogs are now split into two modules using partial
classes. That eliminates a lot of the "Compiler-generated, Don't
touch this" blocks within the code you're editing.

Of course if there is a tool that will convert the older format files,
that would be great. Some of my VS2003 dialogs are complex, and I'm
not looking forward to recreating them. I guess I could study the
newer output format and try to duplicate it, but that may be
time-consuming as well.


Just occurred to me...Does the porting tool for splitting dialogs
exist already?
Nov 17 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Han | last post: by
1 post views Thread by Cristian | last post: by
4 posts views Thread by musosdev | last post: by
10 posts views Thread by GaryDean | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.