Skip to content
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

[dotnet] use **FromWorkload** for targeting/runtime pack versions #12449

Merged
merged 1 commit into from
Aug 19, 2021

Conversation

jonathanpeppers
Copy link
Member

@jonathanpeppers jonathanpeppers commented Aug 16, 2021

Context: dotnet/sdk#19596
Context: dotnet/android#6184

If we use the version number string of **FromWorkload**, then our
runtime packages don't need to be resolved from a NuGet feed. They can
be resolved from the dotnet/packs directory.

This completely eliminates the need for a NuGet.config file when
building a .NET 6 app with a local build of xamarin-macios.

You will no longer need a feed such as:

<add key="local-dotnet-feed" value="~/src/xamarin-macios/_build/nuget-feed" />

To further clean things up, I removed the need for:

  • Any NuGet feed named local-dotnet-feed
  • $(DOTNET_FEED_DIR)
  • Generation of dotnet/Workloads/NuGet.config

@jonathanpeppers jonathanpeppers added the not-notes-worthy Ignore for release notes label Aug 16, 2021
@jonathanpeppers
Copy link
Member Author

On the Android side we could do this when we got on .NET 6.0.100-rc.1.21412.2.

I'll come back to this after this PR lands: #12357

@vs-mobiletools-engineering-service2
Copy link
Collaborator

🔥 Tests failed catastrophically on Build (no summary found). 🔥

Result file $(TEST_SUMMARY_PATH) not found.

Pipeline on Agent
Merge bb3bf63 into b4e828c

@jonathanpeppers jonathanpeppers force-pushed the dotnet-fromworkload branch 3 times, most recently from c015e7a to 6ea5947 Compare August 18, 2021 18:38
Context: dotnet/sdk#19596
Context: dotnet/android#6184

If we use the version number string of `**FromWorkload**`, then our
runtime packages don't need to be resolved from a NuGet feed. They can
be resolved from the `dotnet/packs` directory.

This completely eliminates the need for a `NuGet.config` file when
building a .NET 6 app with a local build of the xamarin-macios.

You will no longer need a feed such as:

    <add key="local-dotnet-feed" value="~/src/xamarin-macios/_build/nuget-feed" />

To further clean things up, I removed the need for:

* Any NuGet feed named `local-dotnet-feed`
* `$(DOTNET_FEED_DIR)`
* Generation of `dotnet/Workloads/NuGet.config`
@vs-mobiletools-engineering-service2
Copy link
Collaborator

❌ [PR Build] Tests failed on Build ❌

Tests failed on Build.

API diff

✅ API Diff from stable

View API diff

API & Generator diff

API Diff (from PR only) (no change)
Generator Diff (only version changes)

GitHub pages

Results can be found in the following github pages (it might take some time to publish):

Test results

5 tests failed, 138 tests passed.

Failed tests

  • link all/Mac Catalyst/Debug [dotnet]: TimedOut (Execution timed out after 1200 seconds.
    No test log file was produced)
  • link sdk/Mac [dotnet]/Debug [dotnet]: BuildFailure
  • link sdk/Mac [dotnet]/Release [dotnet]: BuildFailure
  • dont link/Mac Catalyst/Debug: TimedOut (Execution timed out after 1200 seconds.
    No test log file was produced)
  • monotouch-test/watchOS 32-bits - simulator/Debug (LinkSdk): Failed

Pipeline on Agent XAMBOT-1104.BigSur'
Merge 549dc28 into 243cc40

@rolfbjarne
Copy link
Member

Test failures are unrelated:

@rolfbjarne rolfbjarne merged commit 8d0c1c9 into dotnet:main Aug 19, 2021
@rolfbjarne rolfbjarne deleted the dotnet-fromworkload branch August 19, 2021 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-notes-worthy Ignore for release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants