Compile errors when upgrading to VS.NET 2003

[Ray Wampler]

According to the information on the Microsoft web site, code written in
VB.NET 2002 can simply be recompiled using VS.NET 2003. However, I have
found that code which compiles cleanly in VS.Net 2002 gets new compile
errors in VS 2003.

It appears that there are new scope rules in VB.NET 2003. I get "Name not
declared" errors on public functions in public modules. The errors are
fixed by wrapping the module in a name space and then adding an "imports"
for the name space in other modules that reference the public functions.

I've searched the MSDN KB, but could find no reference to language changes
between VB.Net 2002 and 2003. Does anyone have a list of language changes
or differences in compiler switches to would help someone wanting to upgrade
from VS.Net 2002 to VS.Net 2003?

Thanks,

Ray Wampler
Technical Director, 81x.com

[Adam Braden]

Can you post the repro code? In a simple app I wasn't able to repro what
you described.

--
Thanks,
Adam Braden, VB Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "PresterJohn" <pr*********@comcast.net>
| Newsgroups: microsoft.public.dotnet.languages.vb
| References: <OQ**************@TK2MSFTNGP11.phx.gbl>
| Subject: Re: Compile errors when upgrading to VS.NET 2003
| Lines: 29
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <yKd4b.310899$YN5.213365@sccrnsc01>
| NNTP-Posting-Host: 12.228.154.243
| X-Complaints-To: ab***@comcast.net
| X-Trace: sccrnsc01 1062299678 12.228.154.243 (Sun, 31 Aug 2003 03:14:38
GMT)
| NNTP-Posting-Date: Sun, 31 Aug 2003 03:14:38 GMT
| Organization: Comcast Online
| Date: Sun, 31 Aug 2003 03:14:38 GMT
| Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.co
m!prodigy.com!in.100proofnews.com!in.100proofnews. com!cycny01.gnilink.net!cy
clone1.gnilink.net!wn14feed!wn13feed!wn11feed!worl dnet.att.net!204.127.198.2
03!attbi_feed3!attbi.com!sccrnsc01.POSTED!not-for-mail
| Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.languages.vb:132742
| X-Tomcat-NG: microsoft.public.dotnet.languages.vb
|
| http://www.gotdotnet.com/team/change...1/default.aspx
|
|
| "Ray Wampler" <Ra*@nospam.com> wrote in message
| news:OQ**************@TK2MSFTNGP11.phx.gbl...
| > According to the information on the Microsoft web site, code written in
| > VB.NET 2002 can simply be recompiled using VS.NET 2003. However, I have
| > found that code which compiles cleanly in VS.Net 2002 gets new compile
| > errors in VS 2003.
| >
| > It appears that there are new scope rules in VB.NET 2003. I get "Name
not
| > declared" errors on public functions in public modules. The errors are
| > fixed by wrapping the module in a name space and then adding an
"imports"
| > for the name space in other modules that reference the public functions.
| >
| > I've searched the MSDN KB, but could find no reference to language
changes
| > between VB.Net 2002 and 2003. Does anyone have a list of language
changes
| > or differences in compiler switches to would help someone wanting to
| upgrade
| > from VS.Net 2002 to VS.Net 2003?
| >
| > Thanks,
| >
| > Ray Wampler
| > Technical Director, 81x.com
| >
| >
|
|
|