-
Notifications
You must be signed in to change notification settings - Fork 64
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
Issues when using DNT with newest Visual Studio Build Tools 17.8.0 #136
Comments
I am also facing similar problem |
Having the same problem after updating to VS 17.8.0. Seems the issue is DNT is specifically only targeting up to .net 7 currently. |
it is possible that the environment variables are affected and DNT is not able to locate the path of the same |
I managed to do a .NET 8 build. changed the TargetFrameworks to net8.0 in both projects (Dnt.Commands and Dnt), adapted to changes when removing the outdated Nuget packages. Not too hard, if it helps I can fork and upload my changes. |
Waiting for a new version of DNT with .NET 8 target. In the meantime I found a workaround in my machine: After that DNT returned to work. |
I am having the same issue. @ssteiner can you share your changes with a PR? |
Installing the .NET 6.0 SDK is a valid workaround but it would be better to have a new version with this fixed. @ssteiner could you submit a PR if you have it ready? |
@sturlath : I'm now using version 1.9.0.0 which supports .NET 8 natively. Not using my fork anymore - so I don't see the need for a PR. Or do you want to make your own build anyway? |
Hi, we're using dnt to switch our solution from packages to projects in a Azure DevOps Build Pipeline.
After updating the VS Build Tools to version 17.8.0 (.net 8) DNT is failing with the message below:
Is there a new version for .net 8 already planned?
Can't wait to update my Self Hosted Build agent to the newest version :-)
Regards meister-d
The text was updated successfully, but these errors were encountered: