-
Notifications
You must be signed in to change notification settings - Fork 55
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
Problem loading plugin after updating the project to use VST.NET v2.1.1 #70
Comments
Yeah, I screwed up. I am interested in the changes you made to |
I changed the target framework from "net6.0" to "net8.0" and the version from "6.0.0" to "8.0.0". After those changes the plugin loads fine, when compiled using .Net 8.0, of course. Good luck, and thanks for the great work you've done with this library, hope you can fix it.
|
From the implementation in PublishCommand.cs it looks like you are copying the runtimeconfig.json you use to the deploy directory, which is as following: {
"runtimeOptions": {
"tfm": "net6.0",
"framework": {
"name": "Microsoft.WindowsDesktop.App",
"version": "6.0.0"
}
}
} The dotnet host read this file and will try to boot the user code with .Net 6 runtime, which will fail when the target code is compiled with anything other than I guess the fix would be to create that file by code based on the user code's runtime version, something similar to the following (replaces Line157): File.WriteAllText(
$$"""
{
"runtimeOptions": {
"tfm": "{{userTargetFrameworkMoniker}}",
"framework": {
"name": "Microsoft.WindowsDesktop.App",
"version": "{{userWindowsDesktopFrameworkVersion}}"
}
}
}
""", targetPath, overwrite: true
) Of course, we need to figure out |
My plugin was working fine using VST.NET 2.1.0 and targeting .NET 6.0.
After updating the VST.NET nuget package to 2.1.1 the plugin stops loading in any Host.
I managed to make it work again by targeting .Net 8.0 and
changing the version in the *.runtimeconfig.json file in the "deploy" folder accordingly.
Not sure where the problem is but v2.1.1 seems to be working with .Net 8.0 only.
The text was updated successfully, but these errors were encountered: