.NET 3.5 Software Launch Condition fails

[rho]

Hi,

I've a setup, where I set .NET 3.5 as a Software launch condition.
On a Server 2008 R2 (64bit) this condition fails to detect the missing .net 3.5 version.
The server has these packages installed:

.NET 1.0 Not Installed.
.NET 1.1 Not Installed.
.NET 2.0 SP Version: 2.
.NET 3.0 Not Installed.
.NET 3.5 Not Installed.
.NET 4.0 Full SP Version: No.
.NET 4.0 Client SP Version: No.

.net 2 and 4 are installed, but not 3.5

I'm using AI 8.6 enterprise

[Bogdan]

This happens because .NET 3.5 is included into .NET 4.0. So if your application requires resources from version 3.5 it should work just as well
on a machine where .NET 4.0 is installed.

Regards,
Bogdan

[rho]

If my program is compiled against 3.5, it will search for the 3.5 assemblies at runtime. Therefore I get the following error at runtime:
"System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral ..."

[mihai.petcu]

Hello,

I have discussed this issue with the development team and we will investigate to find a solution to your problem.
As a meanwhile workaround, you could also try to modify the condition manually using the table editor( LaunchCondition table ).

We'll get back to you as soon as we have any conclusive result.

All the best,
Mihai

[rho]

Thanks alot.
As I need .NET 3.5 SP1 at minimum (SP1 brings further classes), I used a registry search to identify it, using the info from http://support.microsoft.com/kb/318785/en-us

[mihai.petcu]

Hello,

After further investigation it seems you can configure your application to use .NET 4.0 as well.
You can edit your application's configuration file( e.g. <YourApplication>.exe.config ) adding the following elements:

Code: Select all

<configuration>
  <startup>
    <supportedRuntime version="v4.0"/>
  </startup>
</configuration>

All the best,
Mihai

[davidhomer]

Hi,

I've had a similar problem - .NET 4.0 does include things like System.DirectoryServices.AccountManagement that we use in .NET 3.5.1 however unlike previous versions of .NET Framework they have no longer included the previous versions in .NET 4.0 but have instead replaced them with new .NET 4.0 versions.

I think you can either reference the new .NET 4 versions (i.e. make your application a .NET 4 application) or you need to use an AdvancedInstaller Prerequisite to check the following is true
HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\SP = 1

As .NET Framework 3.5.1 can either be installed (Windows 2003) or installed as a feature (Windows 2008 R2 etc) we don't direct them to a download but configure the prerequisite to goto a page on our web site that explains what's happening!


Thanks,


Dave