754014e711
* WIP
* Update all the workload names to be net6 versions. This is needed in 7 but NOT in 6.
Dotnet workload install wasm-tools-net6 should install a different set of components than wasm-tools
* Add localization to net7 and correct localization for net6 to target that workload
* Update to 6.0.9 which should be the next version of emsdk.
* Update the net7 and net6 workloads to rename all sdk packs
* Use localize data from net7 project
* Fix typo
* Fix typo
* Update KnownRuntimePack mono versions without clearing them all
* Add net6.0 to description and fix up emscripten-net6 reference
* Fix emsdk version number
* depend on microsoft-net-sdk-emscripten-net7
* Fix missing .net7 renames
* Update WorkloadManifest.targets.in
Don't use **FromWorkload** for pack versions because it doesn't understand the name aliasing we have to use with runtime packs
* Update workload manifest to fix names
* Update the emscripten manifest dependencies
* Use full hash
* WIP: install workload combos for testing
* Update Versions.props
Use Pacjjag6.0.8 packages for the moment because they should be in dotnet-public
* Update emsdk dependencies to `7.0.0-rc.1.22418.3`
* Update emscripten to 7.0.0-rc.1.22418.6, and 6.0.4
* wip
* Fix conditions in WorkloadManifest.targets
* Fix up running WBT
* Fix build
HACK: to work around an incorrect condition in emscripten's
WorkloadManifest.targets which causes emscripten packs not to get
imported.
* Update WorkloadManifest.targets.in
* Update WorkloadManifest.targets.in
* Fix dotnet path references for workload testing
* InstallWorkloadFromArtifacts: don't delete the target path between different requests, clean up before starting
* Fix PackageVersionNet6=6.0.8
* WorkloadManifest.targets: rename some properties to be internal, and versioned
* More renames to fix builds
* Update Versions.props
* Fix up a condition in WorkloadManifest.targets
* Work around the import troubles
* Work around the import troubles
* Revert broken version check
* Use BrowserWorkloadDisabled which will be set in both cases
* Fix typos in WorkloadManifest.targets
* Wasm.Build.Tests: Workaround a msbuild bug causing mysterious failures
When running a fresh build with `dotnet build`, the first one works
fine. But all the subsequent builds fail with no info in the logs at
all.
```
$ /workspaces/runtime/artifacts/bin/dotnet-net7/dotnet build
MSBuild version 17.4.0-preview-22413-01+f0a66ec43 for .NET
Build FAILED.
0 Warning(s)
0 Error(s)
```
And it seems to be related to msbuild nodes, so disable NodeReuse.
* cleanup
* Remove a bunch of stale logic from WBT
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Co-authored-by: Marc Paine <marcpop@microsoft.com>
Co-authored-by: Ankit Jain <radical@gmail.com>
|
||
|---|---|---|
| .config | ||
| .devcontainer | ||
| .github | ||
| docs | ||
| eng | ||
| src | ||
| .clang-format | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .markdownlint.json | ||
| .vsconfig | ||
| build.cmd | ||
| Build.proj | ||
| build.sh | ||
| CODE-OF-CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| Directory.Solution.props | ||
| dotnet.cmd | ||
| dotnet.sh | ||
| global.json | ||
| LICENSE.TXT | ||
| NuGet.config | ||
| PATENTS.TXT | ||
| README.md | ||
| SECURITY.md | ||
| THIRD-PARTY-NOTICES.TXT | ||
.NET Runtime
This repo contains the code to build the .NET runtime, libraries and shared host (dotnet) installers for
all supported platforms, as well as the sources to .NET runtime and libraries.
What is .NET?
Official Starting Page: https://dotnet.microsoft.com
- How to use .NET (with VS, VS Code, command-line CLI)
- Install official releases
- Install daily builds
- Documentation (Get Started, Tutorials, Porting from .NET Framework, API reference, ...)
- Supported OS versions
- Roadmap
- Releases
How can I contribute?
We welcome contributions! Many people all over the world have helped make this project better.
- Contributing explains what kinds of contributions we welcome
- Workflow Instructions explains how to build and test
- Get Up and Running on .NET Core explains how to get nightly builds of the runtime and its libraries to test them in your own projects.
Reporting security issues and security bugs
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Also see info about related Microsoft .NET Core and ASP.NET Core Bug Bounty Program.
Filing issues
This repo should contain issues that are tied to the runtime, the class libraries and frameworks, the installation of the dotnet binary (sometimes known as the muxer) and installation of the .NET runtime and libraries.
For other issues, please use the following repos:
- For overall .NET SDK issues, file in the dotnet/sdk repo
- For ASP.NET issues, file in the dotnet/aspnetcore repo.
Useful Links
- .NET Core source index / .NET Framework source index
- API Reference docs
- .NET API Catalog (incl. APIs from daily builds and API usage info)
- API docs writing guidelines - useful when writing /// comments
- .NET Discord Server - a place to discuss the development of .NET and its ecosystem
.NET Foundation
.NET Runtime is a .NET Foundation project.
There are many .NET related projects on GitHub.
- .NET home repo - links to 100s of .NET projects, from Microsoft and the community.
- ASP.NET Core home - the best place to start learning about ASP.NET Core.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.
General .NET OSS discussions: .NET Foundation Discussions
License
.NET (including the runtime repo) is licensed under the MIT license.