Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugging fresh clone gives "RunCommand property is not defined"

See original GitHub issue

I can successfully build the latest develop branch commit, but when I try to debug I get the following error (manually running .paket\paket restore made no difference).

What steps will reproduce this issue?

Do a fresh clone of https://github.com/MahApps/MahApps.Metro.git

Open src\MahApps.Metro.sln. Wait 1min for it to load. Output is this:

[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\InputDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\MessageDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\MessageDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\LoginDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\ProgressDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\ProgressDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\LoginDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net45\Themes\Dialogs\InputDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net47\Themes\Dialogs\ProgressDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net47\Themes\Dialogs\ProgressDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net47\Themes\Dialogs\MessageDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net47\Themes\Dialogs\MessageDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\LoginDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\ProgressDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\ProgressDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\MessageDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\InputDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\LoginDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\InputDialog.g.cs'.
[Failure] Could not find file 'C:\Users\johnb\Desktop\MahApps.Metro\src\MahApps.Metro\obj\Debug\net40\Themes\Dialogs\MessageDialog.g.cs'.

Select MahApps.Metro.Demo as the startup project.
Build Solution (F6). I get “build succeeded”. Output is this.
Start Debugging (F5). I get, Unable to run your project. The "RunCommand" property is not defined.
I tried .paket\paket restore, no change.

Environment

MahApps.Metro Latest develop branch, also happend with v1.6.2
Windows OS 10
Visual Studio 2017 Community (15.7.1)
.NET Framework 4.0, 4.5, 4.6, 4.7

Issue Analytics

State:
Created 5 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

JVimescommented, Sep 4, 2018

Thanks, @punker76, I got it working. I was missing the .NET Core SDK and the .NET Framework 4.7 SDK.

Also, some order of operations lead it to link v3.1.0 of Costura.Fody, which gave build error, “Method not found Fody.TypeSystem Fody.BaseModuleWeaver.get_TypeSystem()”. I cleared my NuGet caches and now it links Costura.Fody v2.0.0 and builds.

I ran into other quirks (errors when running .paket\paket restore before building in Visual Studio, having to build twice on a clean repo, one other I forget), but now I can’t repro them. I wonder if clearing NuGet caches does good things for the MahApps.Metro build. Thanks again.

0reactions

punker76commented, Sep 4, 2018

@JVimes Any chance to test it again with the latest dev source and these hints https://github.com/MahApps/MahApps.Metro/wiki/Building-the-MahApps.Metro-solution ?

Top Results From Across the Web

Visual Studio Help - The "RunCommand" property is not ...

I have updated and set Server side(API) project as "Single startup project". Rebuild solution and error "RunCommand" property is not defined" ...

Debugging fresh clone gives "RunCommand property is ...

I can successfully build the latest develop branch commit, but when I try to debug I get the following error (manually running .paket\paket ......

Unable to run your project. The "RunCommand" property is ...

Describe the bug. I am not able to debug the project. I get this error. image ; Expected Behavior. debugging should work ;...

[Solved]-Visual Studio Help - The "RunCommand" property is ...

i have updated and set server side(api) project as "single startup project". rebuild solution and error "runcommand" property is not defined"resolved.

How I solved and debugged my Webpack issue through ...

When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.