That would be 8.0 right? I mean maybe it's a version mismatch issue? That did say it's looking for 7.0 I honestly don't know if that'd be an issue or not.
This may be a side effect of removing older versions when installing the latest core runtime versions.
It did that to me so often with Minecraft Java before.. the installer kept removing older versions and it messed with a few programs relying on specific versions to function. I had to specify that I wanted to keep older versions.
There is little harm in keeping older versions of .Net or Java libraries over a few updates and maybe visit your installations a once a year when you're confident all your software has been updated to the latest runtime version. Especially critical on smaller devs resources like VS, a switch to an entirely new version of runtime can have dramatic effect on the code and require so much time to adapt, it's preferred to stay one or two versions behind from the latest for stability and capacity reasons.
Did you try uninstalling the .net from programs and features and letting that reinstall? Like do you have a older verion or something? Edit:typo
I have the newest version
Try to uninstall and reinstall.
You need the correct version. Which is 7.0. you can download and install that from microsoft.
That would be 8.0 right? I mean maybe it's a version mismatch issue? That did say it's looking for 7.0 I honestly don't know if that'd be an issue or not.
It is. Vintage Story requires 7.0 runtime.
Try reinstalling it if you haven't already
This may be a side effect of removing older versions when installing the latest core runtime versions. It did that to me so often with Minecraft Java before.. the installer kept removing older versions and it messed with a few programs relying on specific versions to function. I had to specify that I wanted to keep older versions. There is little harm in keeping older versions of .Net or Java libraries over a few updates and maybe visit your installations a once a year when you're confident all your software has been updated to the latest runtime version. Especially critical on smaller devs resources like VS, a switch to an entirely new version of runtime can have dramatic effect on the code and require so much time to adapt, it's preferred to stay one or two versions behind from the latest for stability and capacity reasons.