When using a non-SDK style project, Visual Studio has troubles when managing non stable dependencies of stable NuGet packages.
This is a known issue and an exchange on the topic has been made with Microsoft here.
Eyeshot 2024.1 relies on SharpGLTF.Toolkit that, even if it is very mature in content, won't be published as a stable release due to a decision of its developer, as stated by them in this issue in the project page.
Nevertheless, solutions are possible in order to correctly install it in order to install stable releases of Eyeshot: you can try and use one of the following approaches in order to solve this Nuget package installation issue.
Solutions
We suggest updating to Eyeshot 2024.2 or later, which relies on the stable SharpGLTF.Toolkit package.
If this is not possible, here are some alternatives:
Upgrade to NET6+ or to the new SDK-style format
Visual Studio improved NuGet management for NET6+ and for SDK-style projects; if you can manage to upgrade to NET6 or at least to the new SDK-style format, you should be able to install stable releases of Eyeshot without facing any issue and no manual operations will be needed. The procedure is described in a paragraph of this article.
Set PackageReference as default package management format
If you must keep the old legacy style for projects, you could set PackageReference as default package management format in the NuGet tool options.
Manually install SharpGLTF.Toolkit
If you must keep the old legacy style for projects, you can manually install the SharpGLTF.Toolkit package before installing the Eyeshot packages.
Be sure that Include prerelease option has been checked whilst looking for the given package.
Comments
Not knowing much about Winforms development, I originally selected the new project type of :
Winforms App (.net framework)
Rather than the more up-to-date, but less obvious :
Winforms.App
The older version of .net used by the "Winforms App (.net framework)" option produces the
SharpGLTF.Toolkit error straight away. The other option doesn't. So that might be why someone sees this error.
Hi Matthew,
yes, that's the reason: by selecting Winforms App (.net framework) you create a non-SDK style project, whilst by selecting Winforms.App the project template creates a SDK-style structure for the csproj.
As stated above, non-SDK style project may have issues in managing non stable dependencies for stable NuGet packages.
It is a visual studio c++ cli project and we are using framework 4.8 is it ok? . Any missing or dependencies we have to install first?
Please sign in to leave a comment.