I've been thinking... (.NET 1.1 and .NET2.0)

[ChrisM]

I've got a medium sized project written in C# for .NET1.1 the project is
live, but still under constant development. There seems to be a lot of new
stuff in .NET2.0 that I'm missing out on, and now they're starting to talk
about .NET3.0, I don't want to get left too far behind.
What are the main issues (if any) porting a project from 1.1 to 2.0? Is it a
case of just opening the project in 2.0, is there likely to be any problems
in doing this?
Anyone got experience of moving a medium sized project from 1.1 to 2.0
that'd like to share their knowledge?

Thanks,

Chris.

 

[Oenone]

Anyone got experience of moving a medium sized project from 1.1 to 2.0
that'd like to share their knowledge?

I moved quite a substantial set of VB.NET applications from 1.1 to 2.0
shortly after 2.0 was released. The transfer was very quick and easy. The
only issue I had was with a very small number of methods that had been
deprecated in 2.0 and marked with the Obsolete attribute, but in each case
there was a straightforward replacement function.

The most time-consuming part of the process was removing all the unused
variables that the new VB compiler can warn me about (no such feature was
available in VS2003).

YMMV of course, but here it was as simple as I could have hoped for.

 

[Guest]

I've ported about a half-dozen VS 2003 projects to VS 2005 - some small and
others I would consider medium to large size.

Most everthing ports okay. I would recommend that if your application does a
lot of database work via dataadapters - that you make sure you read up and
are ready for the new TABLEADAPTER in VS 2005. This is the part of upgrading
to VS 2005 that can really snag you.

It doesn't really hit you during the conversion from VS 2003 to VS 2005 -
because the converter will convert everything to pretty much run right after
the conversion. The instance you try to modify or change a dataadapter that
has been run through the converter however, this is where you can really get
bit - because the whole dataadapter approach has been re-vamped under VS
2005. They (MS) wants you to go with the TABLEADAPTER instead - so it leaves
a need to come up with a strategy FAST.

Other than the tableadapter / dataadapter issue(s). The conversion up is
pretty straightforward...

....and yes you are are right - it is pretty valuable to think about getting
up to VS 2005 before too long. Not necessarily because of falling too far
behind, but the added functionality etc. in VS 2005 is worth the effort ...