Dennis,
In addition to the other comments:
| Are there any "special items" that cannot be converted automatically from
| VB2003 to vb2005?
I have not seen any modifications to my source files when I open a VB 2003
project in VB 2005. Only solution & project files have changed as they have
a new format.
| I am considering upgrading to VB2005 but don't want to
| spend weeks converting "special items" like I did when I upgraded from
VB3.0
| to vb5.0.
Your app should continue to run "as is" under VB 2005. As MS tried to
minimize breaking changes.
Depending on what you've used (System.Web.Mail &
System.Configuration.ConfigurationSettings for example) there are the
namespaces, types, and/or members that are now obsolete & have been replaced
with new namespaces, types, and/or members. However you can continue to use
the old namespace, type, or member as it has simply been marked as Obsolete
& you receive a compile time warning. NOTE: System.Web.Mail has been
replaced with System.Net.Mail which is significantly more powerful.
There are some things, such as the DataGrid being "replaced" by the
DataGrivView, however the DataGrid is still available & not obsolete , its
not on the toolbar. Another example is the original Splitter control & the
new SplitterContainer control. The original Splitter control is not
obsolete, however its not in the ToolBox by default.
Some of the new warnings may pop up more then some of us care for them to
(such as the new "Variable 'x' is used before it has been assigned a value.
A null reference exception could result at runtime")
Of course there is the totally new functionality like Master Pages that you
need to review if you choose to migrate to.
--
Hope this helps
Jay [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
| Are there any "special items" that cannot be converted automatically from
| VB2003 to vb2005? I am considering upgrading to VB2005 but don't want to
| spend weeks converting "special items" like I did when I upgraded from
VB3.0
| to vb5.0.
|
| --
| Dennis in Houston
|
|
| "Jay B. Harlow [MVP - Outlook]" wrote:
|
| > Andy,
| > In addition to the other comments.
| >
| > VS 2005 will convert VS 2003 or VS 2002 projects to the new VS 2005
project
| > format. This conversion is one way. In that you will not be able to open
the
| > converted project in either VS 2002 or VS 2003.
| >
| > VS 2005 does not rely on VS 2002 or VS 2003 for this conversion.
| >
| > Code project had a utility that would convert a VS 2003 project to the
VS
| > 2002 format, however I have not looked for a similar utility for VS 2005
| > yet.
| >
| > --
| > Hope this helps
| > Jay [MVP - Outlook]
| > ..NET Application Architect, Enthusiast, & Evangelist
| > T.S. Bradley -
http://www.tsbradley.net
| >
| >
| > | > | Hi
| > |
| > | As I try to learn VB programing I've been playing around with
sourcecode
| > | from projects hosted on sourceforge. If I open this code in VB 2005
(it is
| > | originally developed in VB 2003), it will automatically upgrade to VB
| > 2005?
| > |
| > | /Andy
| > |
| > |
| >
| >
| >
