• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Are you asking why it doesn't work on your machine, or a more general question as to why it doesn't appear to make use of .NET 4?
 
.NET applications using the 2.0 CLR (.NET 3.5, .NET 2) can't run on .NET 4 automatically.

The easier solution is of course to have .NET 3.5 installed as well then the application will automatically pick the correct CLR to run the .NET app. There is however a way to enable CLR 2.0 applications on just the .NET 4.0 runtime, it requires a app.config (myexefilename.exe.config) with a compatibility setting enabled. Some quick googling found this, I have it working on one of my apps but I can't remember if this is correct.

<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
</configuration>

Here's the compatibility page for .NET if you want more.
http://msdn.microsoft.com/en-us/library/ff602939.aspx
 
Last edited:
It's a more general question. I'm just curious, but if you can explain me this issue I'll be very grateful.
Sorry no, that would take one of the core designers and developers. We forum volunteers aren't privy to that kind of detailed inside information.
 
.NET applications using the 2.0 CLR (.NET 3.5, .NET 3) can't run on .NET 4 automatically.

The easier solution is of course to have .NET 3.5 installed as well then the application will automatically pick the correct CLR to run the .NET app. There is however a way to enable CLR 2.0 applications on just the .NET 4.0 runtime, it requires a app.config (myexefilename.exe.config) with a compatibility setting enabled. Some quick googling found this, I have it working on one of my apps but I can't remember if this is correct.

<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
</configuration>

Here's the compatibility page for .NET if you want more.
http://msdn.microsoft.com/en-us/library/ff602939.aspx

Many thanks Wrathe. I tried google myself, but without any right results and my knowledge of software isn't too good.
Uninstaling .NET 4 was the first thing I've made or second (first was a launching game straight from ck2.exe file - it was too tempting to wait). Now I'm using .NET 3.5 and everything is just fine. Once again thank you for all information they are very usefull.

Sorry no, that would take one of the core designers and developers. We forum volunteers aren't privy to that kind of detailed inside information.

Thanks for interest. I appreciated it.
 
.NET applications using the 2.0 CLR (.NET 3.5, .NET 2) can't run on .NET 4 automatically.

The easier solution is of course to have .NET 3.5 installed as well then the application will automatically pick the correct CLR to run the .NET app. There is however a way to enable CLR 2.0 applications on just the .NET 4.0 runtime, it requires a app.config (myexefilename.exe.config) with a compatibility setting enabled. Some quick googling found this, I have it working on one of my apps but I can't remember if this is correct.

where can I find this app for 4.0 and where should i put it? my problem is I cant use 3.5, due to an reason unknown..
which config do I have to place in which folfer exactly? thx a lot!
 
The app.config in .NET is a xml file that is placed in the same folder as the exe file. I'm currently not on a computer with CK2 installed so I can only guess the name, but if the launcher is named "ck2.exe" then the app config needs to be named "ck2.exe.config" in the same folder. The content of the file should be something like this.

<?xml version ="1.0"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
</configuration>

Of course I have no idea how paradox has made the launcher but this is how I solved the issue with my own application where a customer only wanted to install .NET 4 and still use one of our .NET 3.5 applications.
 
thank you so much Wrathe. After I got it it was quite easy to solve this problem. so kind of you to help me, although you are not near the game ATM. ;D