Update .NET version about avrdudess HOT 8 CLOSED

Ah yeah, .net 2 is rather old now :P It was used mainly for compatibility with Windows XP and 7 which I think came with .net 2.0 already loaded so no fussing around, back when the project started in 2013. I'm just about to release v2.7 now, so I'll have a look at updating for v2.8.

from avrdudess.

That one line seems to have done the trick! I didn't know it could load multiple frameworks depending on what's installed :O Though, there's also a TargetFrameworkVersion / TargetFrameworkVersions option in avrdudess.csproj. I'll have to experiment a bit with a system that only has .net 2.0 installed and see what happens with TargetFrameworkVersion at 4.0 and supportedRuntime as 2.0 and other things. Thanks!

from avrdudess.

Don't get me wrong, avrdudess is awesome, and I believe the only thing preventing it from greater use, is that nobody wan't to install any old .NET version, not already present. (Remember the horrible waiting to install all .NET deps in Win XP?)

Would it be possible to convert the project to use MinGW?
That way (I think) you could drop all .NET stuff!

from avrdudess.

MinGW is for C/C++, right? It would take waaaaayyy too much time and effort to port everything to that, while still maintaining cross-platform compatibility.

from avrdudess.

Yeah, removing .NET may not be possible at this point. But while we investigate, it should be quite straight forward for you to update to use .NET 4.5. Please consult:

• https://docs.microsoft.com/en-us/dotnet/framework/deployment/initialization-errors-managing-the-user-experience
• https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5

HEY THIS FIXED IT!! Yaayh!! 🥇 🎉 ❤️

Add a file called: avrdudess.exe.config with the content:

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

from avrdudess.

Funny enough, there's a file called App.config which should have similar content...but only has 2.0.xxxx, and seem to be missing exactly one line...

from avrdudess.

Ok, so the supportedRuntime stuff works great on a .net 2.0 system! However, targeting a newer framework doesn't work too well (kinda expected there, tested on Windows XP):
4.6.1: "Not a valid windows program"
4.0: "Encountered a problem and needs to close"
3.5: Works, but if any new 3.5 stuff is used (like LINQ to XML) then the JIT debugger will pop up with a bunch of errors about missing references and things.

I also can't seem to get multiple framework targets working either, seems to default to 4.0.

So we'll keep the target framework as 2.0 so no newer things are added by mistake, and add the supportedRuntime line so older .net frameworks don't need to be installed on to newer systems :D

from avrdudess.

great! 👍

from avrdudess.