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