By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,275 Members | 936 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,275 IT Pros & Developers. It's quick & easy.

Upgrading VB2003 to 2005

P: n/a
Couple of questions about upgrading an existing installation of VB2003
(Pro) to 2005 (Pro):

1. Not having dabbled in VB2005 yet, I'd feel more comfortable also
keeping a working VB2003 environment available to me for program
maintenance etc. Is there likely to be any problem in doing this?

And, as an addendum to this question and something that may be obvious
but not to me! To what extent is VB2005 tied to v2.0 of the Framework?

I have programs deployed created with VB2003 to run with v1.1 of the
Framework. I don't necessarily want to _force_ users to upgrade
immediately to v2 of the Framework - though I'd encourage them to do
so as soon as it was convenient. But does this mean that any
maintenance that I do on existing programs should be done under VB2003
to preserve full compatibility with v1.1 Or perhaps/probably there's
simply an option within VB2005 to continue using v1.1 of the
Framework, even though I guess none (or not all??) of the new language
features would work.

2. I always had a problem with my VB2003 installation that when asking
to see any (local) online VB documentation (or when compiling a
program) a Windows Installer dialogue comes up which takes maybe a
minute in 'Gathering Required Information' and then displays 'Error
1606: Could not access network location wwwroot$ Unable to get
security info for this object.' though the correct page eventually
displays. (This is running under WinXPSP2 with a non-admin login.)

I'd obviously like to correct this problem (or more specifically to
ensure that it doesn't happen again) in the new VB2005 installation.
Anyone recognise this issue and can identify what might be wrong?
Maybe it's as simple as I have to use an admin login, but I'd rather
not if possible?

Many thanks
JGD
Feb 8 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
VS2003 is tied to Framework v1.1, VS2005 is tied to Framework v2.0

If you wish to maintain your working VS2003 apps, do not bring them
into VS2005. Once you bring them into VS2005, it will conver them and
then they need to run on v2.0 of the framework.

I have both v1.1 and v2.0 installed on my machine and both VS2003 and
VS2005.

A couple of webapps, I have upgraded because all I needed to do was
upgrade IIS to framework v2.0, the windows forms apps I keep in VS2003
so I don't need to upgrade the clients to framework v2.0, plus if you
convert your apps, you usually need to make a couple of code changes
otherwise vs2005 complains about deprecated code practices.

this is from my experience.

dkode

Feb 8 '06 #2

P: n/a

<dk****@gmail.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
A couple of webapps, I have upgraded because all I needed to do was
upgrade IIS to framework v2.0

this is from my experience.


Does it actually /matter/ to a Framework 1.1 appliction if I upgrade
IIS to Framework 2.0?

Will my application (aspx + compiled dll) continue to run under
Framework 1.1, or will IIS try to "force" it to run under Framework 2.0?

TIA,
Phill W.
Feb 8 '06 #3

P: n/a
If you stay with VS 2003 for now, ensure that you test your app on both 1.1
and 2.0 of the framework. There are some undocumented behavioral changes.
One in particular the caused us a problem was Hashtable access - in 1.1 and
2.0 beta certain types of Hashtable lookups where the key didn't exist should
have raised exceptions, but were silently ignored, while in 2.0 release they
(correctly) raise exceptions (this is not documented).
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: C# to C++ converter & VB to C++ converter
Instant J#: VB to J# converter

"John Dann" wrote:
Couple of questions about upgrading an existing installation of VB2003
(Pro) to 2005 (Pro):

1. Not having dabbled in VB2005 yet, I'd feel more comfortable also
keeping a working VB2003 environment available to me for program
maintenance etc. Is there likely to be any problem in doing this?

And, as an addendum to this question and something that may be obvious
but not to me! To what extent is VB2005 tied to v2.0 of the Framework?

I have programs deployed created with VB2003 to run with v1.1 of the
Framework. I don't necessarily want to _force_ users to upgrade
immediately to v2 of the Framework - though I'd encourage them to do
so as soon as it was convenient. But does this mean that any
maintenance that I do on existing programs should be done under VB2003
to preserve full compatibility with v1.1 Or perhaps/probably there's
simply an option within VB2005 to continue using v1.1 of the
Framework, even though I guess none (or not all??) of the new language
features would work.

2. I always had a problem with my VB2003 installation that when asking
to see any (local) online VB documentation (or when compiling a
program) a Windows Installer dialogue comes up which takes maybe a
minute in 'Gathering Required Information' and then displays 'Error
1606: Could not access network location wwwroot$ Unable to get
security info for this object.' though the correct page eventually
displays. (This is running under WinXPSP2 with a non-admin login.)

I'd obviously like to correct this problem (or more specifically to
ensure that it doesn't happen again) in the new VB2005 installation.
Anyone recognise this issue and can identify what might be wrong?
Maybe it's as simple as I have to use an admin login, but I'd rather
not if possible?

Many thanks
JGD

Feb 8 '06 #4

P: n/a
CMM
You can install 1.1 and 2.0 on an IIS machine at the same time... and you
can run both 1.1 and 2.0 web applications at the same time. However, a web
application can only use one of the frameworks (this is obvious, no?). In
IIS, you control this via the ASP.NET tab in the application's Properties
window. There you control "This app runs in 1.1", "This app runs in 2.0"

The frameworks are designed to run side-by-side. But, obviously an
application can only be written for (compiled to) a particular framework.
Feb 8 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.