Adds instructions to use VS as a tool to debug CLI builds
Previously the coreclr debugging docs only mentioned workflows for Visual Studio
which involve using VS for both building and debugging. This adds an additional
method to build using CLI scripts and use VS to only debug.
Thank you @AaronRobinsonMSFT for showing me this method.
* Update dotnet10 feeds
* Update hardcoded old TFM values
* More hardcode updates and TFM checks
* Updates and delete duplicate file in Bcl.Numerics
* Linker stays on net9.0
* Fix .NET SDK max supported version
* Update apicompat sfx apicompat baseline file
* Update Microsoft.NET.WebAssembly.Threading APICompat settings
* Fix DiagnosticSource build
* Update SDK to RC1 for needed GetAlternateLookup API
to be able to build System.Text.Json on net9.0.
* Fix APICompat runtime regex pattern
* Suppress Bcl.Memory compatibility error for dropped framework
* Fix BinaryFormatter tests regex pattern for version subsitution
* Update BinaryFormatterTests.cs
* Pin SdkVersionForWorkloadTesting to the version in global.json
* Treat net9 and net10 as current for now
* Bump MicrosoftDotNetILCompilerVersion
* Update BinaryFormatterTests.cs
* Update System.Resources.Extensions
* Update AutoImports as well
* Fix ImporterTests.cs
* Block failing SignalRClientTests
* Update XmlSerialzation Schema Import tests.
* Update Versions.props
* Update CompatibilitySuppressions.xml for System.Numerics.Tensors
* Don't set EnableDefaultCompileItems, it doesn't work since we set EnableDefaultItems=false higher up
* Update regex in legacy BinaryFormatterTests.cs too
* Hardcode BinaryFormatter test assembly version to 9.0
This allows us to not change the majority of the tests
* Fix typo
* Fix issue in Microsoft.NET.Workload.Mono.Toolchain.Current.Manifest.pkgproj
* Replace ForceNet8Current in a few more places
* Fix wasi workload
* Fix TreatAsCurrent for 10.0
* Add net9 workload manifests
* Update PackageId in icrosoft.NET.Runtime.WebAssembly.Templates.csproj
* Update ApiCompatBaseline.NetCoreAppLatestStable.xml
Changes from https://github.com/dotnet/runtime/pull/107758
* Remove duplicate dotnet10 feeds from nuget.config
* Update Versions.props
* Fake SDK band version for now
* Update Versions.props
* Update the SDK band versions for real
* Update the dotnet/sdk dependencies
* Update emsdk to net10 workloads
* Install a 9.0 runtime for workload tests too
* Update the compat tasks
* Merge in changes from net10-manifests
* Tmp: Trying out @am11's branch.
* Tmp2: Trying out @am11's branch.
* Tmp3: Replace the last usage of main in clone action.
* Update eng/pipelines/coreclr/templates/build-perf-bdn-app.yml
Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com>
* Update eng/pipelines/coreclr/templates/perf-job.yml
Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com>
* Update eng/pipelines/runtime-wasm-perf.yml
Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com>
---------
Co-authored-by: Larry Ewing <lewing@microsoft.com>
Co-authored-by: Jackson Schuster <36744439+jtschuster@users.noreply.github.com>
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Co-authored-by: Ilona Tomkowicz <itomkowicz@microsoft.com>
Co-authored-by: Steve Molloy <smolloy@microsoft.com>
Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com>
- Remove all IBC comments from the vm portion of the codebase
- Remove `m_GenericTypeDefToCanonMethodTableMap` and `m_MehtodDefToPropertyInfoMap` which were only filled in by NGen
- Remove a variety of flags enums which are never used
- Remove infra for testing Zap and IBC scenarios
- Remove ZapDisable as @egorbo suggested
In Visual Studio 17.5, Visual Studio will start enforcing signature validation for DAC and DBI. This adds documentation on how to disable this for folks using daily or private builds.
* Quality Week 2022: The First Step to a Better Documentation.
* Removed the Markdown Extension's additional development tags.
* Removed redundant stuff.
* Removed redundant stuff.
* Removed guide testing versions to avoid confusion that they would be the only supported versions.
* Addressed some Powershell comments, added a pointer to a yaml with links to other .NET sibling repos, and did a couple mini-corrections. Still got a few comments to address...
* Fixed a ';:' with Powershell's syntax.
* Addressed review comments: Redaction improvements, localization url's, improved code snippets, added info on individual subsets building configurations, changed COMPlus for DOTNET, and other misc improvements.
* Addressed remaining comments.
* Addressed some last comments regarding corerun, and the subset flags in the build scripts.
Co-authored-by: Ivan Diaz <bluehorizon186@gmail.com>
* Fix typos
* Cleanup trailing whitespaces in committed files
* Revert a macro for win32 compat
* Disambiguate test data method
* Revert XMLPath test which rely on external assets
* Revert whitespace change in Xml tests
* Revert ClrEtwAl and ILLink.Shared
* Revert crossgen2 props/targets and *.wxl
* Add MachO dump writer to createdump
Instead of the hacky ELF core dumps on MacOS now createdump generates true MachO dumps.
Setting the COMPlus_DbgEnableElfDumpOnMacOS environment variable is no longer needed.
Add special thread info memory region containing the OS thread ids missing from macho core dumps. This allows SOS to map the thread indexes to thread ids. The address (0x7fffffff00000000) of this special memory region is above the highest user address (0x0007FFFFFFFFF000) and below a kernel reserved address (0xffffff8000xxxxxx) which is kind of moot because dumps don't include any kernel regions. lldb seems just fine with this memory region.
The changes include ARM64 support also, but since I don't have a M1 device I can't build/test them. I'm hoping Steve can at least review them.
Add --verbose/TRACE_VERBOSE support to tone down all the macho dump generation spew.
Issue: #48664
* Fix build problem
* Update docs
* Code review feedback
Co-authored-by: Juan Sebastian Hoyos Ayala <juhoyosa@microsoft.com>
* Make JitDump label output multi-thread safe
`s_compMethodsCount` is a static variable and incrementing it when
two JITs are running at the same time can result in inconsistent labels. This PR fixes it by adding an instance variable `compMethodID` on `Compiler` object and setting it to the value of `s_compMethodsCount` after incrementing it using `InterlockedIncrement()`.
Changed the type of `s_compMethodID` to `LONG` to match the signature of `InterlockedIncrement()` and made it private.
Fixes#10984
* Move files into hierarchy
* fix more links
* Fix botr and features links
* Remove bad apostrophe
* spelling
* Apply suggestions from code review
Co-Authored-By: Youssef Victor <31348972+Youssef1313@users.noreply.github.com>
* Update docs/coding-guidelines/package-projects.md
Co-Authored-By: Jan Kotas <jkotas@microsoft.com>
Co-authored-by: Youssef Victor <31348972+Youssef1313@users.noreply.github.com>
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
Max Charlamb