[JOmsfn]

Hi, new member here. Leaning to slipstream XP for work.

I ONLY have .NET 4 installed on XP Pro SP3. Both the 'Client Profile' and 'Extended' versions. Starting the application file 'nLite.exe' displays '.NET framework initialization error - unable to find a version of the runtime to run this application'. The installation choices were 'english' 'download framework now? NO' and the default settings for the rest of the install which completes successfully. This is the latest version. I have tried both download options and same result. Registry keys verify both .NET 4 installations.

Question: Is this a bug to be fixed in a future update?

I will install latest version of .NET 3.5, try again and update this post. I prefer not to install multiple .NET frameworks but maybe that is to be expected with Microsoft.

Thanks

[bphlpt]

Unfortunately you are doomed to disappointment. If you use enough other software you will eventually discover that you will probably need 2.0, 3.0, 3.5, and 4.0. The 3.5 package will probably install 2.0 and 3.0 for you. There are even rarer cases where you might even need 1.1. Yes, that is partly MS, but mostly it is poorly designed apps that check for specific versions rather than capabilities.

Even if it is a "bug" it will not be fixed and there will never be any further updates for nLite or communication from the developer. He is no longer involved with the development and the source is closed. What you've got is all you will ever get.

Cheers and Regards

This post has been edited by bphlpt: 11 February 2012 - 02:21 AM

[Kelsenellenelvian]

I need to bring up another point:

nLite is NOT for buisness uses! (It's in the license that you agreed to when you installed it)

[boooggy]

.net 4 does not run .net 2 programs, that is not a bug....
u got to thank m$ for that.

[tomasz86]

Actually many files from different Frameworks do overlap each other. The problem is that applications often look specifically for .NET 2.0, 3.0 or other version folder in %WINDIR%\Microsoft.NET\Framework. They may be hard-coded to look for files in v2.0.x folder and won't find them even if they're present in v3.0 or v4.0.x