.NET 8.0 -- Across the Board... #380
Replies: 2 comments 5 replies
-
|
Hi @davidcorbin-atmosera can you point out some examples of what you're referring to? We're in the process of making a release of the Toolkit which has 8.0 as a supported target. There were breaking changes to RID handling made in .NET 8, so it took us a bit to update our bit. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the response. After hours here [EST - Florida]. I could not get any of the samples to run. So I pulled the Source Code, and even GenerateAllSolutions fails. At the end of the work day, I had pulled down the code for https://github.com/microsoft/slngen/ and was just starting to get into that (because it also will not run on a machine with just the latest Win11, VS-2022, and .NET 8.0. Even the Upgrade tool was not sufficient. If you want Ican (when I get back to my work environment in the morning) post more details. The RID issue I was aware of [as per https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/8.0/rid-graph] but it does not see to end there... slngen seems to be upset with some of the aspects of some of the project file formats.. I do have with me a note that the error messages were of the form: |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: This may be a red-herring...] In the file: There is a reference to: Debugging SlnGen shows that the $(MSBuildExtensionsPath)\Microsoft is good, but there is NO WindowsXaml sub-directory there... So is an inevitable failure..... However, I do seem to have all of the workloads for VS-2022.... so further investigation continues.... |
Beta Was this translation helpful? Give feedback.
-
|
OK, though the above was throwing exceptions (and I see nothing exceptional about this environment)... it looks like the original error message results from
in at Line #37.... So continuing to chase the rabbit.... |
Beta Was this translation helpful? Give feedback.
-
|
OK, a little more isolation [stince I can now debug inside of SlnGen :)
is an older project and attempting to open in VS-2022 [17.8.4] says it requires an upgade.... but when loaded via MsBuild it triggers the loadingof Older NuGet packages which later result in the msbuild.sdk.extras being (apparently) an older version than the actual SDK version so things go south from there... At least that is my analysis so far... |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for digging into this @davidcorbin-atmosera, appreciate the efforts. It'd be good to understand what's happening here, as we haven't seen this type of environment issue elsewhere. I've just setup a new devbox myself and repulled these projects and haven't encountered an issue yet. FYI @Arlodotexe as he's also been working on updating our Wiki for the project build requirements: https://github.com/CommunityToolkit/Windows/wiki/Quick-Start If something is missing here, it'd be good to know. Generally, running the bat file from the VS Developer Prompt should just install slngen and open the solution with the dotnet tools command when the proper workloads and Windows SDK are installed. |
Beta Was this translation helpful? Give feedback.
-
|
Actually, I had forgotten about this issue, just filed with details here, but I don't think this sounds the same as what you've been hitting: CommunityToolkit/Tooling-Windows-Submodule#183 |
Beta Was this translation helpful? Give feedback.
-
So many things are still pointing to .NET 6.0 and there are breaking changes (in many ways) to .NET 8.0 --
Is there a curated collection of links (source, documents, samples, et. al.) that only contains material that is ready to go with .NET 8.0 ??
Beta Was this translation helpful? Give feedback.
All reactions