Skip to content

Conversation

@radical
Copy link
Member

@radical radical commented Sep 29, 2022

  • Use latest sdk for workload testing
  • Better isolate nuget restores for test projects
  • Fix issue with mysterious dotnet run --no-build failures due to MSBuildSDKsPath getting forced to be ""
  • Improve the code to use one source to decide which tfm to use
  • Use rollForward=latestMajor for WasmAppHost, because it is being built with a 7.0 sdk, but run with 8.0 sdk.

@radical radical added arch-wasm WebAssembly architecture area-Build-mono labels Sep 29, 2022
@ghost ghost assigned radical Sep 29, 2022
@ghost
Copy link

ghost commented Sep 29, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

null

Author: radical
Assignees: -
Labels:

arch-wasm, area-Build-mono

Milestone: -

- Use only one source of which tfm to use
- Allow a different tfm for blazor
- Add `dotnet8` nuget feed for tests
- Support more than one choice for nuget.config, like for net7, or net8
This was necessary because on windows the tmp path is very long, causing
the test project paths to become too long causing build failures.
`MSBuildSDKsPath` is set by runtime repo, and that interferes with the
test projects. To avoid this the `MSBuildSDKsPath` was set to `""` in
the test environment. But even that can negatively affect the build
because msbuild treats environment variables as "global properties" that
cannot be changed. This manifests when running:

`$ dotnet run --no-build`

.. it would fail with `/foo/bar.csproj is not a valid project file`.

Instead, explicitly *remove* `MSBuildSDKsPath` from the environment when
invoking the process.
.. instead of depending on *one* runtime pack version. This is needed
when we have more than one workload installed.
.. because we explicitly set `NUGET_PACKAGES` envvar now.
@radical radical marked this pull request as ready for review September 29, 2022 16:54
@radical radical merged commit b1c0fe9 into dotnet:main Oct 3, 2022
@radical radical deleted the wbt-fixes branch October 3, 2022 22:42
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-wasm WebAssembly architecture area-Build-mono

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants