Installing a VS2003 App under Framework 2.0

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I currently have an application which is written in (VB).Net 2003 (and hence
uses Framework 1.1). I wish to install it on a user workstation which has
Framework 2.0 but not 1.1 installed. When I run the .msi, it says I must
install Framework 1.1. However this PC is locked down and I can not install
1.1. How can I install the windows app on this PC?
Thanks in advance.
 
Two options:

If you have the source code then upgrade the project to .Net 2.0 in visual
studio 2005.

If you don't have the source code, log on to the machine with an admin
account and install .Net 1.1.
 
Hi,

Unfortunately, the folks who administer the PC do not want to 'install old
software' (Framework 1.x) since Framework 2.0 has updated functionality and
will 'emulate' 1.x.

We have ordered copies of Visual Studio 2005 with our internal purchasing
department, they have been approved and ordered, but have not yet been
received.

Do I have a third option?

Thanks.
 
The third (or more) option(s) may be:

1. Not let your installation package to check whether .NET framework is
installed or which version is intstalled. If you know there is the same
version or later version of .NET framework. Simply install your app.

2. Do not use installation package. Simply XCopy everything of your app to
installation folder. .NET make this very easy.

3. Presuade the administrator to install the .NET framework you app needs.
With 2.0 available, it does not necessarily mean that 1.0 and 1.1 is that
old. If he think so, then he does not understand .NET well: .NET is designed
to run side-by-side with multiple version. Although, with only newer version
installed, not app developed on older version would run well most likely, it
is not 100% guaranteed. The only sure way to guarantee a .NET app run as it
should is to run it on the version of the framework it was developed on. If
your app is developed on 1.1, and you canot afford to spend more time to
test if it is OK on .NET2.0, why waste time to make the possible
change/testing? Simply install .NET 1.1 would be the simplest and safeset
thing to do.
 
Back
Top