Skip to content

Conversation

@MichalStrehovsky
Copy link
Member

@MichalStrehovsky MichalStrehovsky commented Nov 12, 2024

I wasn't able to run ILLink unit tests in VS without doing this. My steps:

  • build.cmd tools.illink+tools.illinktests
  • open src\tools\illink.sln in VS
  • right click Mono.Linker.Tests project and choose Run tests
  • CS0006 Metadata file 'D:\git\runtime2\artifacts\bin\ILVerification\Debug\ILVerification.dll' could not be found Mono.Linker.Tests D:\git\runtime2\src\tools\illink\test\Mono.Linker.Tests\CSC 1
  • Add ILVerification project to the SLN
  • Try running tests again
  • MSB3030 Could not copy the file "D:\git\runtime2\artifacts\obj\coreclr\cdac-build-tool\Debug\apphost.exe" because it was not found. Mono.Linker.Tests C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets 5321
  • Exclude cdac-build-tool from building unless we need the CoreCLR VM (in separate PR Only build cdac-build-tool when we need to build runtime #109719)
  • Try running tests again
  • Success

Cc @dotnet/illink

I wasn't able to run ILLink unit tests in VS without doing this. My steps:

* build.cmd tools.illink+tools.illinktests
* open src\tools\illink.sln in VS
* right click Mono.Linker.Tests project and choose Run tests
* CS0006	Metadata file 'D:\git\runtime2\artifacts\bin\ILVerification\Debug\ILVerification.dll' could not be found	Mono.Linker.Tests	D:\git\runtime2\src\tools\illink\test\Mono.Linker.Tests\CSC	1
* Add ILVerification project to the SLN
* Try running tests again
* MSB3030	Could not copy the file "D:\git\runtime2\artifacts\obj\coreclr\cdac-build-tool\Debug\apphost.exe" because it was not found.	Mono.Linker.Tests	C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets	5321
* Exclude cdac-build-tool from building unless we need the CoreCLR VM
* Try running tests again
* Success
@ghost ghost added the area-Tools-ILLink .NET linker development as well as trimming analyzers label Nov 12, 2024
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Nov 12, 2024
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.

Copy link
Member

@sbomer sbomer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

@MichalStrehovsky
Copy link
Member Author

/ba-g browser tests timing out but this is not a product change

@MichalStrehovsky MichalStrehovsky merged commit eee9fd3 into dotnet:main Nov 12, 2024
@MichalStrehovsky MichalStrehovsky deleted the ilverifylink branch November 12, 2024 21:47
mikelle-rogers pushed a commit to mikelle-rogers/runtime that referenced this pull request Dec 10, 2024
I wasn't able to run ILLink unit tests in VS without doing this. My steps:
@github-actions github-actions bot locked and limited conversation to collaborators Dec 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Tools-ILLink .NET linker development as well as trimming analyzers linkable-framework Issues associated with delivering a linker friendly framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants