-
Notifications
You must be signed in to change notification settings - Fork 830
Update DEVGUIDE.md and dev container for non-released SDK usage #18716
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
Conversation
|
Co-authored-by: vzarytovskii <[email protected]>
Co-authored-by: vzarytovskii <[email protected]>
DEVGUIDE.md how to use plain dotnet build with non-released SDKsCo-authored-by: vzarytovskii <[email protected]>
…regular usage Co-authored-by: vzarytovskii <[email protected]>
Co-authored-by: vzarytovskii <[email protected]>
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addressesI tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot no, revert the last commit |
…ntainer" Co-authored-by: vzarytovskii <[email protected]>
Reverted the last commit - DOTNET_ROOT and PATH environment variables are now restored to the remoteEnv section. (7e0b28c) |
Co-authored-by: vzarytovskii <[email protected]>
When working with non-released .NET SDKs (as specified in
global.json), developers encounter a confusing error message when trying to use plaindotnet build:While the error message provides the solution, it's not very visible and lacks context about why this happens or how to set up the environment properly.
Changes Made
📚 Enhanced Documentation
Added a comprehensive "Working with non-released .NET SDKs" section to
DEVGUIDE.mdthat:global.jsonspecifies non-released SDK versions./eng/common/dotnet.shbefore building🐳 Improved Dev Container Experience
Updated
.devcontainer/devcontainer.jsonto:DOTNET_ROOTandPATHenvironment variables.dotnetdirectory exists and when using system SDKExample Usage
After these changes, developers can:
The dev container now "just works" without requiring manual SDK setup.
Testing
These minimal changes significantly improve the developer experience when working with non-released SDKs by making the setup process more visible and user-friendly.
Fixes #18715.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
1k9vsblobprodcus379.vsblob.vsassets.io/usr/share/dotnet/dotnet restore ./FSharp.Compiler.Service.sln(dns block)/usr/share/dotnet/dotnet restore FSharp.Compiler.Service.sln(dns block)4vyvsblobprodcus361.vsblob.vsassets.io/usr/share/dotnet/dotnet restore ./FSharp.Compiler.Service.sln(dns block)/usr/share/dotnet/dotnet restore FSharp.Compiler.Service.sln(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.