Migrating to VS 2005

  • Thread starter Thread starter wandii
  • Start date Start date
W

wandii

Hi,
I have written couple of projects which include several crystal reports
in VS.net 2003
(VB.Net) and company would like to move to VS 2005. What
does it take to convert to Visual Studio.Net 2005? Can the 2003 project
just
be opened up in 2005? Will that convert it. The interface for 2005 very

different from 2003. I got the VS 2005 professional edition - can 2003
and 2005
be installed on the same machine and run side by side. Please advice
what steps
should I take to do the migration to VS 2005. Thanks for the
assistance.

Regards,
Wan
 
First off, it's quite simple to move from 2003 to 2005. The source
typically doesn't change, just the project/solutions. We've migrated
quite a few over and not run into any difficulties.

To answer your second question, you can just as easily have both 2003
and 2005 running on the same machine, I have had both for over 6 months
now. I rarely use 2003 anymore and I'm just keeping it loaded in case
I've missed a project somewhere.

Hope this helps,
 
Side by side installations aren't a problem at all.

As a tip, I would suggest changing the file association for .sln files to
"Microsoft Visual Studio Version Selector". That way 2003 projects will
open in 2003 and 2005 projects will open in 2005 (default is to open
everything in 2005 which you may not want). To convert a project from 2003
to 2005, select to open the project from within 2005 --- the conversion
process will kick off automatically. -- Note that the conversion can't be
undone. (short of restoring a backup of the converted project)
 
wandii said:
I have written couple of projects which include several crystal reports
in VS.net 2003
(VB.Net) and company would like to move to VS 2005. What
does it take to convert to Visual Studio.Net 2005? Can the 2003 project
just
be opened up in 2005? Will that convert it. The interface for 2005 very
Click to expand...

There were heavy changes in ASP.NET. Windows Forms applications migrate
more cleanly but the new partial class form model won't be generated
automatically for the converted forms. In addition, some of the .NET 1.*
classes are now deprecated, such as 'System.Web.Mail'.
 
Thank you all for your feedback.
As a tip, I would suggest changing the file association for .sln files to
"Microsoft Visual Studio Version Selector". That way 2003 projects will
open in 2003 and 2005 projects will open in 2005 (default is to open
everything in 2005 which you may not want).
Click to expand...

Matt - Could you please give me little more information on "changing
the file association for .sln files to "Microsoft Visual Studio Version
Selector". Do I need to do this before the
conversion. Is there a setting options in VS 2003/2005.

Also I came across another thread which states that when VS 2005
converts
VS.net2003 project, it will create a "Backup" folder to store the old
VS.net2003 solution. Is this correct? Please advice. Thanks in
advance.

Regards,
Wan
 
What took the place of system.web.mail?

Herfried K. Wagner said:
There were heavy changes in ASP.NET. Windows Forms applications migrate
more cleanly but the new partial class form model won't be generated
automatically for the converted forms. In addition, some of the .NET 1.*
classes are now deprecated, such as 'System.Web.Mail'.
Click to expand...
 
yeah.. ever since 'the great brainwash'

this thread is like asking 'is it easy to learn astrophysics once you
know quantum physics'

it's irrelevent.

the punchline is.. who gives a ****... vb is a dead language

move back to VB6 or do java / c#..

vb.net has already been killed

the latest programming survey merely confirms that microsoft killed off
the worlds most popular language-- without a decent alternative..

we used to have a single damn language for macros, etl, applications.
dhtml

now we can't do that without 3 distinct languages-- in addition to vb6

..net is a travesty; the people that made it should be in JAIL or DEAD,
bludgeoned by the angry masses.

the NEW French Revolution-- kick those ****ing pigs off of their
****ing BMWs and make them start listening to CUSTOMERS and DEVELOPERS

DEVELOPERS, DEVELOPERS, DEVELOPERS???? From what I've seen Ballmer's
out of ****ing touch with reality; and we need GATES BACK.

And that Ray Ozzie dude? **** his Ajax, Xml smoking cocksucker ass.

Bring back VISUAL AND BASIC

we have been treated unfairly at every turn; and I am sick and tired of
you guys bickering about a DEAD LANGUAGE.

-aaron
 
The file association I'm referring to is the windows file association. To
change file associations, open windows explorer, then "tools" menu, then
"folder options", then "file types" tab. This doesn't really have anything
to do with converting projects, just what version of VS will attempt to open
a solution when opening directly from the file system instead of the
development environment (by double clicking on a .sln file for example). As
for the second question about a 'backup' folder... honestly, I've never had
to roll back a solution, so I couldn't advise intelligently about a backup
folder that might be created. I usually make a habit of keeping a copy of
something that I know could get screwed up before messing with it.
 
Same old story, learn something then it gets trashed 2 years later.
Microsoft are a pathetic company, but they have got worse over the last
5 years.

Stupid marketing
********************
Plenty of retarded marketing that no-one understands. Shrouding their
unwanted products in mystery. Read the web site and try to figure out
what each product "actually does". Steamlines workflow seamlessly -
blah blah ****ing blah - it all means nothing to me - just
unintelligible marketing hype.

Constant change without benefit
*************************************
Invest you time over years learning computer languages and techniques -
only to have the techniques changed every 2 years and languages
discontinued. So you can flush everything you have learned down the
toilet.

What's more the "newer" "better" way is never newer or better.
Instead it is slower - with more code to write, more stupid wizards
that you don't want because you know you can't trust them and must
remain in control.

Changing the way recordsets work so that the underlying format is xml -
even though you don't need or want the additional complexity - as its
unnecessary for a normal database and you don't want to send text
files across the internet for every data use.

Total disregard for customers
**********************************
Despite a disappointed reaction from existing vb 6.0 developers MS
decided to to discontinue Visual Basic 4 years ago. VB.NET (or
whatever their stupid marketing dept is calling it this week) is not
actualy visual basic, it is a different language than vb 6.0, with only
a few syntax similarities. They only called it VB.NET to con the
existing VB 6.0 userbase into trying it - kind of insulting to the
intelligence. That truly is a representation of the despise that they
as a company show towards customers that have purchased products from
them over a number of years. Imagine what the amount would be in
dollars if you calculate the money that companies and individuals have
lost through wasted time since the introduction of vb.net.

I for one do not plan of getting screwed over by Microsoft again. From
now on I will be using open source solutions and programming languages.
Languages that do not leave you at the mercy of these idiots.

The Grand Master
 
Back
Top