A
Agnes
I had create some project in .net 2000. now I will install the new version.
Anything I need to aware or be careful ??
Thanks
Anything I need to aware or be careful ??
Thanks
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
T
TheNedMan
You meant that you're using 2002 of course? (since VS 2000 doesn't
exist).
One thing that really irritated me was that while VS 2002 produces
code that runs on the 1.0 or 1.1 version of the framework with no
work on your part, VS 2003 makes it much harder - you need to
reproduce a pile of incomprehensible statements in a config file to
get this to work.
You might want to wait until VS 2005 to see if they fix this - there's
not much improvement overall in 2003.
exist).
One thing that really irritated me was that while VS 2002 produces
code that runs on the 1.0 or 1.1 version of the framework with no
work on your part, VS 2003 makes it much harder - you need to
reproduce a pile of incomprehensible statements in a config file to
get this to work.
You might want to wait until VS 2005 to see if they fix this - there's
not much improvement overall in 2003.
C
Cor Ligthert
Hi Agnes,
There is no much pain upgrading from 2002 to 2003, you can state it a
disadvantage that your users have to use dotNet 1.1.
In my opinion is 2003 much more robust than 2002, it has less bugs in the
IDE and the upgrade from VB6 to Net is much more complete. You can also
shorten your code a little bit. Maybe you have seen samples here which are
impossible to do with VB2002. It has as well one more control "the
folderdialog". As last the MSI from 2003 is much smaller than with 2002.
There will be more, however that I do not remember me now.
I hope this gives some ideas?
Cor
There is no much pain upgrading from 2002 to 2003, you can state it a
disadvantage that your users have to use dotNet 1.1.
In my opinion is 2003 much more robust than 2002, it has less bugs in the
IDE and the upgrade from VB6 to Net is much more complete. You can also
shorten your code a little bit. Maybe you have seen samples here which are
impossible to do with VB2002. It has as well one more control "the
folderdialog". As last the MSI from 2003 is much smaller than with 2002.
There will be more, however that I do not remember me now.
I hope this gives some ideas?
Cor
H
Herfried K. Wagner [MVP]
* (e-mail address removed)-spam.invalid (TheNedMan) scripsit:
Mhm... VS.NET 2002 will compile .NET 1.1 assemblies, so that's a big
difference. In current development, I would try to avoid to target .NET
1.0 because there is absolutely no reason to stick with .NET 1.0.
ACK, wait if possible but be aware that there will be massive changes.
You meant that you're using 2002 of course? (since VS 2000 doesn't
exist).
One thing that really irritated me was that while VS 2002 produces
code that runs on the 1.0 or 1.1 version of the framework with no
work on your part, VS 2003 makes it much harder - you need to
reproduce a pile of incomprehensible statements in a config file to
get this to work.
Mhm... VS.NET 2002 will compile .NET 1.1 assemblies, so that's a big
difference. In current development, I would try to avoid to target .NET
1.0 because there is absolutely no reason to stick with .NET 1.0.
You might want to wait until VS 2005 to see if they fix this - there's
not much improvement overall in 2003.
ACK, wait if possible but be aware that there will be massive changes.
G
Giuliano
"TheNedMan" <[email protected]> ha scritto nel
messaggio
| One thing that really irritated me was that while VS 2002 produces
| code that runs on the 1.0 or 1.1 version of the framework with no
| work on your part, VS 2003 makes it much harder - you need to
| reproduce a pile of incomprehensible statements in a config file to
| get this to work.
I know that VS2002 compile only 1.0 and with .config you can do whatever you
want.
Do you really know how to edit & compile 1.1 with VS2002 ?
Can you tell me how to do it or where to find info about that ?
Many thanks
Giuliano
messaggio
| One thing that really irritated me was that while VS 2002 produces
| code that runs on the 1.0 or 1.1 version of the framework with no
| work on your part, VS 2003 makes it much harder - you need to
| reproduce a pile of incomprehensible statements in a config file to
| get this to work.
I know that VS2002 compile only 1.0 and with .config you can do whatever you
want.
Do you really know how to edit & compile 1.1 with VS2002 ?
Can you tell me how to do it or where to find info about that ?
Many thanks
Giuliano
J
Jay B. Harlow [MVP - Outlook]
Herfried,
In my experience VS.NET 2002 only compiles .NET 1.0 assemblies, while VS.NET
2003 only compiles .NET 1.1 assembles.
For details of side by side & having an assembly run under a different
version of the framework see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/sidexsidenet.asp
Yes there are unsupported procedures to get VS.NET 2002 to almost create a
1.1 assembly, however in my experience it causes VS.NET 2002 to become even
more unstable then it already is...
Hope this helps
Jay
Is that a typo?Mhm... VS.NET 2002 will compile .NET 1.1 assemblies, so that's a big
In my experience VS.NET 2002 only compiles .NET 1.0 assemblies, while VS.NET
2003 only compiles .NET 1.1 assembles.
For details of side by side & having an assembly run under a different
version of the framework see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/sidexsidenet.asp
Yes there are unsupported procedures to get VS.NET 2002 to almost create a
1.1 assembly, however in my experience it causes VS.NET 2002 to become even
more unstable then it already is...
Hope this helps
Jay
G
Giuliano
"Jay B. Harlow [MVP - Outlook]" <[email protected]> ha scritto nel
messaggio
[cut]
| Yes there are unsupported procedures to get VS.NET 2002 to almost create a
| 1.1 assembly, however in my experience it causes VS.NET 2002 to become
even
| more unstable then it already is...
Which procedures ? Do you have any link ?
Giuliano
messaggio
[cut]
| Yes there are unsupported procedures to get VS.NET 2002 to almost create a
| 1.1 assembly, however in my experience it causes VS.NET 2002 to become
even
| more unstable then it already is...
Which procedures ? Do you have any link ?
Giuliano
J
Jay B. Harlow [MVP - Outlook]
Giuliano,
I use VS.NET 2003, so I don't have the link. It shows up in the general &
framwork newsgroups every once in awhile.
Rather then waste your time on finding the link I would recommend upgrading
to VS.NET 2003.
Just a thought
Jay
I use VS.NET 2003, so I don't have the link. It shows up in the general &
framwork newsgroups every once in awhile.
Rather then waste your time on finding the link I would recommend upgrading
to VS.NET 2003.
Just a thought
Jay
T
TheNedMan
VS 2002 assemblies will run on 1.1. You can't use features from 1.1
since VS 2002 itself runs on 1.0, but my point was that it is
drop-dead easy to produce for any version of the framework with VS
2002 since 1.0 is forward compatible with 1.1.
Look at the documentaion for trying this with VS 2003 - if you're
comfortable with the config file gobbledeegook that you have to
include then go for it. Personally, I don't want to distribute this
sort of crap - I'll wait for 2005 (assuming Microsoft fixes it
there).
since VS 2002 itself runs on 1.0, but my point was that it is
drop-dead easy to produce for any version of the framework with VS
2002 since 1.0 is forward compatible with 1.1.
Look at the documentaion for trying this with VS 2003 - if you're
comfortable with the config file gobbledeegook that you have to
include then go for it. Personally, I don't want to distribute this
sort of crap - I'll wait for 2005 (assuming Microsoft fixes it
there).
H
Herfried K. Wagner [MVP]
* "Jay B. Harlow said:Herfried,
Is that a typo?
As always, it's a typo. I remember that's not the first time I pressed
"2" instead of "3" in posts about this topic :-(.
In my experience VS.NET 2002 only compiles .NET 1.0 assemblies, while VS.NET
2003 only compiles .NET 1.1 assembles.
ACK!
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.