We currently have a rather large application that is in VB.NET 2002. We have
just purchased licenses to the 2003/1.1 Framework version of Visual Studio.
What kind of conversion, if any, will we need to do to move our application
over to the 2003/1.1 version? We will be moving this application over to
production within a couple of months, and I don't want to push that down
because I have to redo a bunch of stuff. However, I feel it is better going
to the 1.1 Framework now rather than waiting and having to do it after it is
in production.

I am hoping it is simply a matter of deinstalling the 2002 Visual Studio;
installing the 2003 version; then loading our application and it converts
anything as needed. Also, will we need to deinstall our 3rd party tools and
reinstall them? (i.e. we have ActiveReports .NET, TrueDBGrid .NET tool sets,
and the VB.NET Resource Kit. Should we also uninstall and reinstall them?)

Is this true? What is involved? Experiences? Thanks in advance.

Tom

* "Tom" <(E-Mail Removed)> scripsit:
> We currently have a rather large application that is in VB.NET 2002. We have
> just purchased licenses to the 2003/1.1 Framework version of Visual Studio.
> What kind of conversion, if any, will we need to do to move our application
> over to the 2003/1.1 version? We will be moving this application over to
> production within a couple of months, and I don't want to push that down
> because I have to redo a bunch of stuff. However, I feel it is better going
> to the 1.1 Framework now rather than waiting and having to do it after it is
> in production.

..NET Framework changes:

<URL:http://www.gotdotnet.com/team/changeinfo/>

> I am hoping it is simply a matter of deinstalling the 2002 Visual Studio;
> installing the 2003 version; then loading our application and it converts

Conversion will be done automatically. VS.NET 2002 and 2003 can be
installed on the same machine, VS.NET 2002 should be installed before
installing version 2003.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

Thanks, Herfried. Unfortunately, I don't have the disk space to have both
the 2002 and the 2003 versions of VS on my machine at the same time. So I
will have to uninstall the 2002 version and then install the 2003 version.

I assume then that no one has had any conversion issues with the 2002 vs
2003 version change?

Tom

"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> * "Tom" <(E-Mail Removed)> scripsit:
> > We currently have a rather large application that is in VB.NET 2002. We
have
> > just purchased licenses to the 2003/1.1 Framework version of Visual
Studio.
> > What kind of conversion, if any, will we need to do to move our
application
> > over to the 2003/1.1 version? We will be moving this application over to
> > production within a couple of months, and I don't want to push that down
> > because I have to redo a bunch of stuff. However, I feel it is better
going
> > to the 1.1 Framework now rather than waiting and having to do it after
it is
> > in production.
>
> .NET Framework changes:
>
> <URL:http://www.gotdotnet.com/team/changeinfo/>
>
> > I am hoping it is simply a matter of deinstalling the 2002 Visual
Studio;
> > installing the 2003 version; then loading our application and it
converts
>
> Conversion will be done automatically. VS.NET 2002 and 2003 can be
> installed on the same machine, VS.NET 2002 should be installed before
> installing version 2003.
>
> --
> Herfried K. Wagner [MVP]
> <URL:http://dotnet.mvps.org/>

Hi Tom

The only problem i had after upgrating was all the
Crystal Reports stopped working !? You have to change the
reference path of your project.

Kind Regards
Jorge

>-----Original Message-----
>We currently have a rather large application that is in
VB.NET 2002. We have
>just purchased licenses to the 2003/1.1 Framework
version of Visual Studio.
>What kind of conversion, if any, will we need to do to
move our application
>over to the 2003/1.1 version? We will be moving this
application over to
>production within a couple of months, and I don't want
to push that down
>because I have to redo a bunch of stuff. However, I feel
it is better going
>to the 1.1 Framework now rather than waiting and having
to do it after it is
>in production.
>
> I am hoping it is simply a matter of deinstalling the
2002 Visual Studio;
>installing the 2003 version; then loading our
application and it converts
>anything as needed. Also, will we need to deinstall our
3rd party tools and
>reinstall them? (i.e. we have ActiveReports .NET,
TrueDBGrid .NET tool sets,
>and the VB.NET Resource Kit. Should we also uninstall
and reinstall them?)
>
>Is this true? What is involved? Experiences? Thanks in
advance.
>
>Tom
>
>
>.
>

There were a few issues I found with 2003. The order of
some of the events for the ComboBox has changed. This
screwed up my lookup-as-you-type functionality I
programmed into my control.

Also, if you have a form and popup another form and keep
the previous in the background (even if it is hidden) then
the Alt-Key combinations don't work properly. For
example, if you have a button with Alt-A on the original
form, and another button with the same Alt-A on the newly
popped up form, the Alt-A won't work at all. You have to
completely unload the original form from memory in order
to get the Alt-A to work on the new form. It only occurs
when you have buttons with the same Alt key combination on
both forms.

I don't remember any other problems (except for the
aforementioned crystal reports issue).

-Lee
>-----Original Message-----
>Thanks, Herfried. Unfortunately, I don't have the disk
space to have both
>the 2002 and the 2003 versions of VS on my machine at the
same time. So I
>will have to uninstall the 2002 version and then install
the 2003 version.
>
>I assume then that no one has had any conversion issues
with the 2002 vs
>2003 version change?
>
>Tom
>
>"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)>
wrote in message
>news:(E-Mail Removed)...
>> * "Tom" <(E-Mail Removed)> scripsit:
>> > We currently have a rather large application that is
in VB.NET 2002. We
>have
>> > just purchased licenses to the 2003/1.1 Framework
version of Visual
>Studio.
>> > What kind of conversion, if any, will we need to do
to move our
>application
>> > over to the 2003/1.1 version? We will be moving this
application over to
>> > production within a couple of months, and I don't
want to push that down
>> > because I have to redo a bunch of stuff. However, I
feel it is better
>going
>> > to the 1.1 Framework now rather than waiting and
having to do it after
>it is
>> > in production.
>>
>> .NET Framework changes:
>>
>> <URL:http://www.gotdotnet.com/team/changeinfo/>
>>
>> > I am hoping it is simply a matter of deinstalling
the 2002 Visual
>Studio;
>> > installing the 2003 version; then loading our
application and it
>converts
>>
>> Conversion will be done automatically. VS.NET 2002 and
2003 can be
>> installed on the same machine, VS.NET 2002 should be
installed before
>> installing version 2003.
>>
>> --
>> Herfried K. Wagner [MVP]
>> <URL:http://dotnet.mvps.org/>
>
>
>.
>

Hi all:

What if I just continue developing my project using VS2002? I have heard
that only 2003 or above can support WinXP (or higher).......

I hope that it's just a rumor...

"Lee Moody" <(E-Mail Removed)> ???
news:f49a01c43dbf$4c6e2030$(E-Mail Removed) ???...
> There were a few issues I found with 2003. The order of
> some of the events for the ComboBox has changed. This
> screwed up my lookup-as-you-type functionality I
> programmed into my control.
>
> Also, if you have a form and popup another form and keep
> the previous in the background (even if it is hidden) then
> the Alt-Key combinations don't work properly. For
> example, if you have a button with Alt-A on the original
> form, and another button with the same Alt-A on the newly
> popped up form, the Alt-A won't work at all. You have to
> completely unload the original form from memory in order
> to get the Alt-A to work on the new form. It only occurs
> when you have buttons with the same Alt key combination on
> both forms.
>
> I don't remember any other problems (except for the
> aforementioned crystal reports issue).
>
> -Lee
> >-----Original Message-----
> >Thanks, Herfried. Unfortunately, I don't have the disk
> space to have both
> >the 2002 and the 2003 versions of VS on my machine at the
> same time. So I
> >will have to uninstall the 2002 version and then install
> the 2003 version.
> >
> >I assume then that no one has had any conversion issues
> with the 2002 vs
> >2003 version change?
> >
> >Tom
> >
> >"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)>
> wrote in message
> >news:(E-Mail Removed)...
> >> * "Tom" <(E-Mail Removed)> scripsit:
> >> > We currently have a rather large application that is
> in VB.NET 2002. We
> >have
> >> > just purchased licenses to the 2003/1.1 Framework
> version of Visual
> >Studio.
> >> > What kind of conversion, if any, will we need to do
> to move our
> >application
> >> > over to the 2003/1.1 version? We will be moving this
> application over to
> >> > production within a couple of months, and I don't
> want to push that down
> >> > because I have to redo a bunch of stuff. However, I
> feel it is better
> >going
> >> > to the 1.1 Framework now rather than waiting and
> having to do it after
> >it is
> >> > in production.
> >>
> >> .NET Framework changes:
> >>
> >> <URL:http://www.gotdotnet.com/team/changeinfo/>
> >>
> >> > I am hoping it is simply a matter of deinstalling
> the 2002 Visual
> >Studio;
> >> > installing the 2003 version; then loading our
> application and it
> >converts
> >>
> >> Conversion will be done automatically. VS.NET 2002 and
> 2003 can be
> >> installed on the same machine, VS.NET 2002 should be
> installed before
> >> installing version 2003.
> >>
> >> --
> >> Herfried K. Wagner [MVP]
> >> <URL:http://dotnet.mvps.org/>
> >
> >
> >.
> >