-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.IO.InvalidDataException: Failed to load configuration from file 'D:\GICutscenes\appsettings.json'. #92
Comments
我已经把 appsettings.json 更新了一遍 |
I have the same issue after updating to 0.5.0
|
I guess it's because the .NET version changed or something? I wish that was mentioned on the releases page. I tried installing .NET 7.0 manually from here but it didn't change anything, but using the standalone build works |
I reverted it back to .NET 6 due to some issues (#86) with the non-standalone builds (and I didn't have the time to investigate further), I forgot to change back the build instruction in the README section. How does your |
I was using the appsettings.json from the zip file, so it included the
|
Got this error too, with .NET SDK 8.0.0-rc2 installed in my system. Seems like the current workaround is to always use the standalone version if you have different .NET version installed. Though I suggest removing the non-standalone package as .NET SDK 8 will be finalized as next LTS version in a few days in fear Windows might update to that and breaking the app |
Is it possible that since this tool uses .NET 6.0 it might not work with only 8.0 installed ? Since the non-standalone version uses the runtime installed on the computer, maybe it causes some parts of the program to malfunction 🤔 |
Hmm I wonder if it's possible to force within the app to use a specific SDK. Though, I'm pretty sure it has something to do with the JSON library used. Try running |
Does not work unfortunately Though, confusingly, even without global.json file it seems to tries to run it with NETCore 6.0.24 still but got an error with it.
|
Alright, seems like it had a compilation problem (managed to get another error related to some libraries), maybe due to a conflict between the CI (which somehow stayed in .NET 7.0) and the program (which specifies .NET 6.0), and since some libraries were close to their 7.0 version, it might be breaking. So it should require an SDK upgrade and I'll try to stabilize everything on .NET 8.0. I'll remove the non-standalone versions for now. |
The text was updated successfully, but these errors were encountered: