<configuration>
<startup>
<supportedRuntime version="v4.0.30319"/>
</startup>
</configuration>
make sure your CLR build version "30319" is what you put in the config file.
> --
> You received this message because you are subscribed to jni...@googlegroups.com
> http://groups.google.com/group/jni4net?hl=en-GB?hl=en-GB
> http://jni4net.sf.net/
>
If this was just on one machine I would agree that there would be a
problem with the machine config, however on two different machines
with a fresh install of VS 2010, I now suspsect there really is an
issue with the proxygen application.
Is there any other logging that I can turn on? I would be glad to test
any code fixes if you would supply them to give you more information
to the problem.
Thanks again for you time on this issue.
<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
</configuration>
I'm glad to hear it :-)
I realized that I could add CLR 4.0 as preferred runtime while
preserving ability to run proxygen on CLR 2.0.
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
<supportedRuntime version="v2.0.50727"/>
</startup>
</configuration>
I added this proxygen.exe.config into binary distribution for next version.
Preview is here:
http://www.ane-kolin.cz/zamboch/jni4net-0.8.5.0-snapshot20110707-bin.zip
I also added new sample runtimeSelection, which could help people to
learn about their runtime versions.
Finally jni4net runtime and proxygen are now dumping runtime versions
when running setup in verbose mode.
Feedback appreciated, thanks!
Pavel