How was your upgrade to VS.NET 2005?

[Brett Romero]

I'm using VS.NET 2003 with Framework 1.1. I want to upgrade to VS.NET
2005 and Framework 2.0. I'd like to hear comments from people that
have moved to the new platform with final releases of VS.NET and the
framework. I'm interested in any installation and code migration
issues you may have had.

Thanks,
Brett

[Peter Bromberg [C# MVP]]

Brett,
First we should clarify that it's not really what could be accurately
described as an "upgrade", since Visual Studio.Net 2003 and the .NET
Framework 1.1 remain on the target machine, completely undisturbed and 100%
usable, when .NET Framework 2.0 and Visual Studio 2005 are installed.

Personally I've had neither installation or code migration issues. Some
projects from VS.NET 2003 will convert without a hitch. Others require some
work. Of course, a conversion won't necessarily take advantage of all the new
features.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Brett Romero" wrote:

I'm using VS.NET 2003 with Framework 1.1. I want to upgrade to VS.NET
2005 and Framework 2.0. I'd like to hear comments from people that
have moved to the new platform with final releases of VS.NET and the
framework. I'm interested in any installation and code migration
issues you may have had.

Thanks,
Brett

[Brett Romero]

Thanks.

Do you know anything about the 2.0 winform Datagrid being extremely
slow:
http://weblogs.asp.net/fbouma/archiv...29/428848.aspx

Brett

[John Vottero]

"Brett Romero" <ac*****@cygen. com> wrote in message
news:11******** **************@ g49g2000cwa.goo glegroups.com.. .

I'm using VS.NET 2003 with Framework 1.1. I want to upgrade to VS.NET
2005 and Framework 2.0. I'd like to hear comments from people that
have moved to the new platform with final releases of VS.NET and the
framework. I'm interested in any installation and code migration
issues you may have had.

A bug (or undocumented breaking change) with the Browsable attribute broke
virtually all of our code but, we're still sticking with VS2005 and V2.0 of
the Framework. There are just way too many new or improved or fixed things
to go back.

[Brett Romero]

What do you mean a "browsable" attribute "broke" all of your code?

Thanks,
Brett

[Steven Nagy]

I just upgraded the other day to use ASP.NET in vs2005.

By default, my code windows load right to left now instead of
traditional left to right.
No doubt this is configurable, but I don't really care that much.

The biggest thing is these "WebParts" which I am yet to play with. I
think they extend other controls.

I migrated my project with no problems. It uses its own data-connecting
technology and it all seems to work ok. So far nothing about the
upgrade has WOWed me, except for the time it took to install. I do like
the Version Selector.. seems to have intelligently worked out which
projects are version 7.1 and which are 8.0. It even changed my solution
icons on desktop with the relative numbers, so I know which version of
VS will load the solution.

I am still quite worried about upgrading some of our other projects,
the windows applications.
There's no reason for this except that I don't want to have to justify
it to my boss if it all goes pear-shaped.

One thing I don't like is that sometimes if I have a ASP script error
somewhere, it comes up with some weird compile errors. Currently I am
looking at a VB file that is called 'App_Web__g_wq4 4j.0.vb' which is
definately not part of my solution. This file has a namespace in it
called 'ASP' ! I am guessing this is something that should be handled
internal and transparent to me, the user. I think its a temp file or
something. The real error is actually back in my script somewhere else,
nothing to do with this weird page. Who knows why it is popping up when
I click on one of the 163 compile errors I get as a result of 1 script
error.

Otherwise, it seems standard to me so far. Hope my random rambling was
entertaining if not useful.

[Brett Romero]

Thanks Steven. What do you mean here, "seems to have intelligently
worked out which
projects are version 7.1 and which are 8.0. It even changed my solution

icons on desktop with the relative numbers, so I know which version of
VS will load the solution. "

I'm guessing 7.1 is VS.NET 2003 (.NET v1.1) and 8.0 is VS.NET 2005
(.NET v2.0).

Are you saying I can still run .NET 1.1 apps with .NET 2.0 and VS.NET
2005 installed? I thought .NET 1.1 apps would not work in VS.NET 2005.

Brett

[Steven Nagy]

Oh yes they all work great. I don't understand that technicals, Peter
is probably the best man for that, but a part of the VS2005 install
includes a Version Selector component.
All my previous file associations (*.SLN) are now associated to the
Version Selector as opposed to either VS2003 or VS2005. The version
selector then loads the right software version.
The actual ICONS have the VS logo, with a little 7.1 (VS2003) or 8.0
(VS2005) in the top right corner of the icon.

Looking at my "Installed Programs" list I actually see 1.1 and 2.0 as
installed items. I am definately still programming in VS2003 and
running those 1.1 windows apps. I am only using VS2005 currently for
web apps.
So the up side of all this is that you can install VS2005 and NEVER USE
IT if you so desire, knowing your apps will still load and run in
VS2003.

Steve

[Brett Romero]

Thanks on all the confirms Steve. Nice.

Brett

[Nick Hounsome]

Are you saying I can still run .NET 1.1 apps with .NET 2.0 and VS.NET
2005 installed? I thought .NET 1.1 apps would not work in VS.NET 2005.

VS2005 cannot BUILD 1.1 apps so if you have 1.1 solutions you need VS2003 to
BUILD them as 1.1 apps.
Alternatively VS2005 can change your slns to 2005 and build them as 2.0 apps