473,323 Members | 1,570 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,323 software developers and data experts.

VB 2002 and 2003 code incompatible?

I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we're an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary

Nov 20 '05 #1
12 1699
The 2 versions use different versions of the .NET Framework. Once a 2002
project has been upgraded to a 2003 project you can't go back.

"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...
I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we're an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary


Nov 20 '05 #2
There are some breaking code changes. By forcing the "gestapo-like" tactics,
Microsoft saves people from themselves (ie, trying to run code with breaking
changes in the older IDE and bombing).

With much of your code, you can simply change the XML and run it.

In general, most 1.0 code runs in 1.1 without any changes, which is good.

--
Gregory A. Beamer
MPV; MCP: +I, SE, SD, DBA

************************************************** ********************
Think outside the box!
************************************************** ********************
"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...
I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we're an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary


Nov 20 '05 #3
Hi,

A free utility to convert vs.net 2003 project to 2002 format.
http://www.thecodeproject.com/macro/...ert%7Cvs%2Enet

Ken
---------------------
"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...
I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we're an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary


Nov 20 '05 #4
Ken, thanks a LOT.

I can understand MS wanting to "SAVE ME from myself" but as I said
if the code remains the same, I see no reason to force feed upgrades
every time MS needs a boost in their revenue stream.

If they can "re-engineer" an O/S and development tools there HAS to be
a way to make writing code with their new tools less of a pain in the arse.


Regards,

Gary
Ken Tucker wrote:
Hi,

A free utility to convert vs.net 2003 project to 2002 format.
http://www.thecodeproject.com/macro/...ert%7Cvs%2Enet

Ken
---------------------
"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...
I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we're an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary




Nov 20 '05 #5
Gary Napolitano <gn****@earthlink.net> wrote in news:3F5B5946.7583D5A8
@earthlink.net:

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.


Actually, if you read the EULA.Txt, you can make a copy and run it at
home as long as you are the only person that runs it. AFAIK, VB has
always allowed this. Here is section 1.1 from the EULA:

1.1 General License Grant. Microsoft grants to you as an individual, a
personal, nonexclusive license to use the Software, and to make and use
copies
of the Software for the purposes of designing, developing, testing, and
demonstrating your software product(s), provided that you are the only
individual using the Software.
If you are an entity, Microsoft grants to you a personal, nonexclusive
license
to use the Software, and to make and use copies of the Software, provided
that
for each individual using the Software within your organization, you have
acquired a separate and valid license for each such individual.

If I am wrong, someone please correct me.

Chris
Nov 20 '05 #6
You can get the 2003 upgrade disks for only $29 from Microsoft. May as well
do it, have a copy at home.

It's irritating, if you look at the version number of vs 2003, it's only
7.1, not 8, really only a minor upgrade (or bug fix collection, the new
features are minor and they haven't fixed major annoyances like combobox not
allowing form keypreview).

Bob

"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...
I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we're an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won't bring 2003 from work
to install at home as I'm certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary


Nov 20 '05 #7
Cor
Hi Bob,

Do you tell that by expirience or from the papers?

Cor
Nov 20 '05 #8
Cor
Herfried,
It's irritating, if you look at the version number of vs 2003, it's only
7.1, not 8, really only a minor upgrade (or bug fix collection, the new
features are minor and they haven't fixed major annoyances like combobox not
allowing form keypreview).

Cor
Nov 20 '05 #9
Hello,

"Cor" <no*@non.com> schrieb:
It's irritating, if you look at the version number of vs 2003, it's only 7.1, not 8, really only a minor upgrade (or bug fix collection, the new features are minor and they haven't fixed major annoyances like
combobox not allowing form keypreview).


The .NET framework is version 1.1 too, not version 2.0.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
http://www.mvps.org/dotnet
Nov 20 '05 #10
Cor
Hi Herfried,
It's irritating, if you look at the version number of vs 2003, it's only
7.1, not 8, really only a minor upgrade (or bug fix collection, the new
features are minor and they haven't fixed major annoyances like combobox notallowing form keypreview).


Did you think I was writing that, that was Bob and I was asking if : Do you
tell that by expirience or from the papers?

How can you think I would write that after all the goods I have told about
VB 2003
:-(((((((((((((((((
Cor
Nov 20 '05 #11
I'm not sure if sarcasm is intended, but I mention the problem with combo
boxes from much experience, as I use a lot of them in my apps, and have to
write much longer code for lack of keypreview functionality if the focus is
on a combo box. It's a known issue with combo boxes with the normal drop
down style. Please correct me if you know otherwise.

Bob
"Cor" <no*@non.com> wrote in message
news:3f***********************@reader20.wxs.nl...
Herfried,
It's irritating, if you look at the version number of vs 2003, it's only
7.1, not 8, really only a minor upgrade (or bug fix collection, the new
features are minor and they haven't fixed major annoyances like combobox not allowing form keypreview).

Cor

Nov 20 '05 #12
Cor
Bob,
Reading it over yes the Combobox is for me to terrible, it was with 2002 and
one of the first things that I did overlook in 2003 was if it was fixed and
as I remember it was not. I had such a same problem with binding from
textboxes and stopped that. That too I don't know if that works now beter.
But a lot of things are better.

But the combobox is so overloaded with members.

Cor
Nov 20 '05 #13

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Don Miller | last post by:
I can't seem to find at MS how to detect the 2002 OS vs. 2003 OS for web applications using ASP. This is the only page I could find...
1
by: Rafael Campana | last post by:
Hi, I posted the messsage below last week, but no replies, I've reproduced the problem with a VB macro, just create one and paste the following code. Let me know of any workarounds you can...
0
by: Ricardo Dias Marques | last post by:
Hi, I have a development machine with Visual Studio .Net 2003 which, as far as I know, targets the 1.1 .Net Framework. Now I need to open some solutions that were created in another machine...
3
by: Larry Pits | last post by:
Hi All, Is there a backward compatability issue regarding to .Net 2002 and .Net 2003? I heard someone said that if you're developing in .Net 2003 and gave the entire project to someone who is...
1
by: zfeld | last post by:
1. Where do I get the Office 2003 PIAs? On the MSDN download site there are only downloads for XP office PIAs. Do they automatically get installed to the GAC with the installation of office 2003? ...
13
by: Noesis Strategy | last post by:
When I ordered my new laptop, Sony didn't offer Access 2003 in its bundles. Recently, I have begun to design Access databases using an copy of Access 2002 from my previous laptop. It works fine,...
7
by: Wayne Aprato | last post by:
I have several Access 2003 mde databases. When I try to open them in Access 2002 I get the following error: "The Visual Basic for Applications project in the database is corrupt." ...
4
by: Jon S via DotNetMonster.com | last post by:
Hi all I've taught myself C# 2002 using VS.NET 2002. I've recently brought myself an ASP.NET 2003 book. I will work through this ASP.NET 2003 using VS.NET 2002 and C# 2002. I don't fully...
52
by: Neil | last post by:
We are running an Access 2000 MDB with a SQL 7 back end. Our network guy is upgrading to Windows Server 2003 and wants to upgrade Office and SQL Server at the same time. We're moving to SQL Server...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.