QModManager does not recognize .NET 3.5 about qmodmanager

[Alexejhero]

Yes, we did not account for this.

[CoreTheCoder]

Thanks for the response. I'll keep an eye out for an updated installer.

[Alexejhero]

Could you please show me a screenshot of your v3.5 registry folder?

[CoreTheCoder]

That's what's attached in my original message.

Edit: Unless i've misunderstood you.

[Alexejhero]

I meant the base v3.5 folder, not the 1033 folder

[CoreTheCoder]

Oh, lol. It's late. Gottcha.

[CoreTheCoder]

I gotta hit the sack. I'll check back in the AM. Best of luck and thanks for looking into this!

[Alexejhero]

Okay, this is actually weird. From what I can tell, it should be detected correctly.

[Alexejhero]

Okay so, news - after inspecting the script I could not find anything that could lead to this error. I have checked my registry and confirmed that it works as it should. Please show me a screenshot of the error that you receive.

[CoreTheCoder]

You got it. Here is everything:

Once UAC is accepted. This box pops up almost instantly.

[CoreTheCoder]

Interesting, even VS is throwing this:

[CoreTheCoder]

I'm now shifting into tracking down WHY it would say i have it, but can't use it in VS.

[Alexejhero]

This is the function that checks for the .NET version.

If VS says that it's missing, it probably is. Check to see if it is enabled from the Turn Windows features on or off menu.

[CoreTheCoder]

That was the first thing i did. It looks a little different on win 7 but it WAS there. I just removed it in an attempt to reinstall that exact feature.

[CoreTheCoder]

This is AFTER uninstalling it. (it was properly checked before) Here is the uninstalled cap of the reg post uninstall:

It's not listed in NDP any more. Gone.. as it should be.

Will now attempt to reinstall 3.5.

[Alexejhero]

From the registry, the installer only checks if the Install key is 1.

The only other explanation is that the registry could not be queried for the key.

[CoreTheCoder]

And here it is again after reinstall of the feature:

I'd imagine if there was something wrong with the reg as global as "unable to read" it would impact.. tons of stuff. I program in .NET mostly without issues. I do exclusively work in .NET 4.0 and above though.

I install .. loads of stuff. Steam library has over 2000 games? I have a few hundred installed right now. Never had a reg related issue of that nature so i'm more inclined to believe it's something else. I'm continuing to work on it. Seeing if i can can get source to load and eventually compile.

[Alexejhero]

Did you reboot your computer after installing?

[Alexejhero]

The only thing I can find on the internet related to this issue is this, but from what I understand you've already tried it.

[CoreTheCoder]

It worked!

Took a few to reboot.

Uninstall and reinstall of 3.5 via windows features was what did it. No idea WHY seeing as how the reg seems fine before the uninstall reinstall.

[CoreTheCoder]

I can also target frame works older than .NET 4.0 in VS2017 now.

Thanks for your help Alex. Keep up the great work!

[CoreTheCoder]

I closed this not realizing you couldn't comment. Thanks again i'll let you close it out!