VS 2003.NET and VS 2005?

[Alain Dekker]

I'm developing VB .NET 1.1 and native VC++ applications in VS2003.NET. One
of our team has started developing in VS 2005 using C# and .NET 2.0. I'd
like to install VS 2005 on my computer, but still to be able to continue
with the VS 2003.NET apps. Are there any gotchas I should be aware of?

Thanks,
Alain

 

[Jason Keats]

I'm developing VB .NET 1.1 and native VC++ applications in VS2003.NET. One
of our team has started developing in VS 2005 using C# and .NET 2.0. I'd
like to install VS 2005 on my computer, but still to be able to continue
with the VS 2003.NET apps. Are there any gotchas I should be aware of?

No. But why not consider VS2010?

 

[Jason Keats]

I'm developing VB .NET 1.1 and native VC++ applications in VS2003.NET. One
of our team has started developing in VS 2005 using C# and .NET 2.0. I'd
like to install VS 2005 on my computer, but still to be able to continue
with the VS 2003.NET apps. Are there any gotchas I should be aware of?

No. But why not consider VS2010?

 

[Alain Dekker]

Hehe. Well, for one thing I don't want to be forced to use .NET 4.0. Besides
which, we ahve licenses for 2003 and 2005, and not 2010.

 

[Alain Dekker]

Thanks

of?

I have VS2003, VS2005, VS2008, and VS2010 on my work machine and using all
of them with no problem.

 

[Alain Dekker]

That is good advice...but the slope is slippery. Using 4.0 might offer more
features, but it also comes at the cost of size and performance, very
noticeable on older hardware. We're working with very price sensitive
hardware, and in a field where any hardware change means a large regulatory
burden, so we don't just change because somebody thinks some new feature is
nifty.

I've also read that you cannot target .NET 1.1 using 2008 and 2010, think
thats right. Only 2.0 and thats not the default.

We are a very small team (only 3 developers) and all working on very
different platforms (one pre-Windows, another Windows CE, another Windows XP
moving onto Windows 7, another a VxWorks deriviative), so if there's not a
product champion to push for (say) 2010, and 2003 or 2005 does the job, its
only natural to stick with what you know.

Thanks for the advice, though.
Alain

 

[kndg]

[...]
IMHO, you and your coworker(s?) should upgrade to VS2010. Use the
Express version if you have to. It's way better than being a decade
behind the rest of the world.

Pete

IMO, based on his other posts (which he mentioned about Win CE), the
best version to upgrade is VS2008. As far as I know, VS2010 does not
support compact framework (please correct me if I'm wrong). I myself
regretting removing my version on VS2008 and found out the smart device
development is not supported in VS2010. (Actually it is not a big deal
as mostly I do smart device development just for hobby).

 

[Alain Dekker]

I've now installed VS 2005 alongside my original installation of VS 2003.NET
and can confirm that everything works nicely. I installed VS 2005 SP1 and
the SP2 for Compact Framework .NET v2.0, and am now developing and deploying
for the Windows CE 5.0 without issue.

I really like the "Version Selector" that is now pointing at SLN files which
correctly opens VS 2003.NET files in that version, and VS 2005 files in that
version. I was really worried it would auto-upgrade everything to VS 2005
with all sorts of issues!

Thanks for the advice.

Regards,
Alain