Hello Carlo,

The and projects are not compatible, nor some of the generated code in
InitializeComponents. Here is what we do: we have VS 2003 and VS 2005
directories dedicated to development. We do not share the physical files
between the solutions, instead they are shared via the source-code control
system. So after we check in changes in one branch or the other, if the file
is shared, the other branch must be updated via get latest version. In the
source code control, most files are shared between the two projects.

All the files which cannot be shared are branched permanently in the source
code control system. However, the windows forms code generated in VS 2003
can be used in VS 2005. This means all your UI work must be done in the VS
2003 directory tree, which works if you have no VS 2005 specific controls.
VS 2003 seems more stable for UI work anyway.

Other work can be done in either version, as long as you use conditional
compilation (#if) to protect the VS 2003 branch from new code  for the .net
framework 2.0.

If you have to permanently branch your UI classes, it is best to reduce them
to only contain a UI and move all logic into classes that can be shared
between the two versions.

That is my best advice.

Regards,
Frank Hileman

check out VG.net: http://www.vgdotnet.com
Animated vector graphics system
Integrated Visual Studio graphics editor