wpf: Can't compile Microsoft.Dotnet.Wpf.sln

.NET Core Version: (e.g. 3.0 Preview1, or daily build number, use dotnet --info) http://json.schemastore.org/global “dotnet”: “5.0.100-preview.1.20155.7”,
Windows version: (Microsoft Windows [Version 10.0.18363.778])
Does the bug reproduce also in WPF for .NET Framework 4.8?: I think no
Is this bug related specifically to tooling in Visual Studio (e.g. XAML Designer, Code editing, etc…)? If yes, please file the issue via the instructions [here] (https://docs.microsoft.com/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2019).
Security issues and bugs should be reported privately, learn more via our responsible disclosure guidelines.

Problem description: When I try to compile Microsoft.Dotnet.Wpf.sln in Microsoft Visual Studio Community 2019 Version 16.5.4 I got 66 error. Here is some of them

============= Severity Code Description Project Project Rank Path File Line Column Category Suppression State Error Intellisense Xml sources not found: IntellisenseXmlDir=C:\Users\BDV\Source\Repos\dotnet-wpf.tools\native\bin\dotnet-api-docs_netcoreapp3.0\0.0.0.2_intellisense\netcore-3.0\ WindowsBase-ref 2 C:\Users\BDV\Source\Repos\dotnet-wpf\eng\WpfArcadeSdk\tools C:\Users\BDV\Source\Repos\dotnet-wpf\eng\WpfArcadeSdk\tools\ReferenceAssembly.targets 53 5

=========== Severity Code Description Project Project Rank Path File Line Column Category Suppression State Error Perl is not found: PerlCommand=“C:\Users\BDV\Source\Repos\dotnet-wpf.tools\native\bin\strawberry-perl\5.28.1.1-1\portableshell.bat” WindowsBase 3 C:\Users\BDV\Source\Repos\dotnet-wpf\src\Microsoft.DotNet.Wpf\src\WindowsBase C:\Users\BDV\Source\Repos\dotnet-wpf\src\Microsoft.DotNet.Wpf\src\WindowsBase\WindowsBase.csproj 373 5

=========== Severity Code Description Project Project Rank Path File Line Column Category Suppression State Error ResolvedImplementationAssembly ‘C:\Users\BDV\Source\Repos\dotnet-wpf\artifacts\obj\PresentationBuildTasks\Debug\netcoreapp2.1\PresentationBuildTasks.dll’ did not exist. PresentationBuildTasks 15 C:\Users\BDV\Source\Repos\dotnet-wpf\eng\WpfArcadeSdk\tools C:\Users\BDV\Source\Repos\dotnet-wpf\eng\WpfArcadeSdk\tools\ApiCompat.targets 133 5

=========== Severity Code Description Project Project Rank Path File Line Column Category Suppression State Error ResolvedImplementationAssembly item must be specified to run API compat. UIAutomationClientSideProviders 15 C:\Users\BDV\Source\Repos\dotnet-wpf\eng\WpfArcadeSdk\tools C:\Users\BDV\Source\Repos\dotnet-wpf\eng\WpfArcadeSdk\tools\ApiCompat.targets 188 5

=========== Severity Code Description Project Project Rank Path File Line Column Category Suppression State Error MSB4057 The target “InitializeSourceControlInformationFromSourceControlManager” does not exist in the project. C:\Users\BDV.nuget\packages\microsoft.dotnet.arcade.sdk\5.0.0-beta.20228.4\tools\Version.targets resources 14 C:\Users\BDV.nuget\packages\microsoft.dotnet.arcade.sdk\5.0.0-beta.20228.4\tools C:\Users\BDV.nuget\packages\microsoft.dotnet.arcade.sdk\5.0.0-beta.20228.4\tools\Version.targets 51 11 sshot-97

Actual behavior:

Expected behavior:

Minimal repro:

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 24 (9 by maintainers)

Commits related to this issue

Remove flacky and redundant codegen I belive that bringing these two relatively simple classes directly in source control will benefit more then attempt to codegen them. Anyway nobody touch them. This... — committed to kant2002/wpf by kant2002 3 years ago
Remove flacky and redundant codegen I belive that bringing these two relatively simple classes directly in source control will benefit more then attempt to codegen them. Anyway nobody touch them. This... — committed to dotnet/wpf by kant2002 3 years ago
Remove flacky and redundant codegen (#4909) * Remove flacky and redundant codegen I belive that bringing these two relatively simple classes directly in source control will benefit more then attempt... — committed to dotnet/wpf by kant2002 2 years ago

Most upvoted comments

Seems to be this issue can be closed after https://github.com/dotnet/wpf/pull/4909. Please open new issue, if some problems will be present.

kant2002 on Feb 25, 2022

I successfully built it in VisualStudio by merged #4909 . Thank you @kant2002

lindexi on Aug 28, 2021

Actually, I want to debug through the FrameworkElement and UIElement classes to understand why the ArrangeOverride method in my control is called so often.

Visual Studio Enable .NET Framework source stepping always uses optimized assemblies, so I can’t view local variables when I step through the FrameworkElement and UIElement source codes.

I thought that using https://github.com/dotnet/wpf.git project, I can compile WPF assemblies in debug mode and fully debug FrameworkElement and UIElement source codes to understand how ArrangeOverride is called for parents and children.

I have the same purpose with you , just debugging and dig deeply into WPF

usernamedd on Jul 29, 2020

How about creating a special version of the repository that would contain the WPF Source + Empty WPF Application.

Getting the DRT’s/tests to build (again) could achieve something like that.

https://github.com/dotnet/wpf/issues/3132

vatsan-madhavan on Jun 22, 2020

@lindexi , @weltkante thank you for helping here. @ryalanms will try to update the build docs as time permits to include the C++CLI requirements.

fabiant3 on Jun 22, 2020

Thanks lindexi, I can’t say yet how much it will help me solve the problem - Full debugging of WPF source codes.

How about creating a special version of the repository that would contain the WPF Source + Empty WPF Application. WPF Sandbox. So the developer could modify Application for the necessary task and debug the code at the WPF Source level.

dmitrybv on May 8, 2020

I completely deleted local WPF folder and cloned the https://github.com/dotnet/wpf.git project from scratch.

Some of the cached folders are in your user user profile, outside the cloned repo, check the comment I linked above it has the paths you need to clear. If it still doesn’t work with the paths I mentioned you have to look closely into the errors in your build script output to identify other cache paths that may have not been cleared yet.

Also you need to execute the build script to download various things, you can’t just open the solution and expect it to build, the first build must be done from console.

weltkante on May 7, 2020