Discussion:
Targeting .Net framework version 3.0.
(too old to reply)
Wake-Up-Jeff
2010-02-08 23:54:57 UTC
Permalink
I have developed a VB.NET application and am trying to target .net framework
V3.0.
The project was initially developed using Visual Studio 2005.
I am now using VS 2008 Professional.
I go to project\properties\compile\advanced compile options.
From the "Target Framework" dropdown list box, I select .NET Framework 3.0.
VS informs me that it needs to close and re-open the project.
Fine.
Once the project is re-opened, I check the setting, and it is still set to
.NET Framework 3.0.
Great.
I rebuild the project and copy the EXE to the destination computer.
When I try to run it, I get a message that the system needs .net framework
v2.0.x in order to run my application.
What am I doing wrong?
Wilson, Phil
2010-02-09 00:01:38 UTC
Permalink
Setup.exe is not integrated with the launch conditions in your setup
project. So if you're running a setup.exe it's going to be using whatever is
set in the Prerequisites button's list, but the MSI will look for whatever's
in the properties in .NET launch conditions.
--
Phil Wilson
The Definitive Guide to Windows Installer
http://www.apress.com/book/view/1590592972
Post by Wake-Up-Jeff
I have developed a VB.NET application and am trying to target .net
framework V3.0.
The project was initially developed using Visual Studio 2005.
I am now using VS 2008 Professional.
I go to project\properties\compile\advanced compile options.
From the "Target Framework" dropdown list box, I select .NET Framework 3.0.
VS informs me that it needs to close and re-open the project.
Fine.
Once the project is re-opened, I check the setting, and it is still set to
.NET Framework 3.0.
Great.
I rebuild the project and copy the EXE to the destination computer.
When I try to run it, I get a message that the system needs .net framework
v2.0.x in order to run my application.
What am I doing wrong?
Wake-Up-Jeff
2010-02-09 10:27:09 UTC
Permalink
I have not used a setup program or an MSI.
I haven't got that far yet.
I am just copying the EXE from the BIN folder on my development machine
directly onto the target machine.
Any advice?
Post by Wilson, Phil
Setup.exe is not integrated with the launch conditions in your setup
project. So if you're running a setup.exe it's going to be using whatever
is set in the Prerequisites button's list, but the MSI will look for
whatever's in the properties in .NET launch conditions.
--
Phil Wilson
The Definitive Guide to Windows Installer
http://www.apress.com/book/view/1590592972
Post by Wake-Up-Jeff
I have developed a VB.NET application and am trying to target .net
framework V3.0.
The project was initially developed using Visual Studio 2005.
I am now using VS 2008 Professional.
I go to project\properties\compile\advanced compile options.
From the "Target Framework" dropdown list box, I select .NET Framework 3.0.
VS informs me that it needs to close and re-open the project.
Fine.
Once the project is re-opened, I check the setting, and it is still set
to .NET Framework 3.0.
Great.
I rebuild the project and copy the EXE to the destination computer.
When I try to run it, I get a message that the system needs .net
framework v2.0.x in order to run my application.
What am I doing wrong?
PvdG42
2010-02-09 15:41:26 UTC
Permalink
Post by Wake-Up-Jeff
I have developed a VB.NET application and am trying to target .net
framework V3.0.
The project was initially developed using Visual Studio 2005.
I am now using VS 2008 Professional.
I go to project\properties\compile\advanced compile options.
From the "Target Framework" dropdown list box, I select .NET Framework 3.0.
VS informs me that it needs to close and re-open the project.
Fine.
Once the project is re-opened, I check the setting, and it is still set to
.NET Framework 3.0.
Great.
I rebuild the project and copy the EXE to the destination computer.
When I try to run it, I get a message that the system needs .net framework
v2.0.x in order to run my application.
What am I doing wrong?
What version(s) of the .NET Framework are on the target machine? You cannot
have 3.0 without 2.0, as 3.0 is an add-on to 2.0, not a self-sufficient
version. Are both the source and target machines patched to exactly the same
point?

Loading...