question-mark
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.

MrAdviceWeaverPath not defined in Xamarin.Android project

See original GitHub issue

In a Xamarin.Android project the latest MrAdvice is failing to run.

 'AssemblyPath' is not recognized as an internal or external command,
 operable program or batch file.
C:\xxxxxxx\packages\MrAdvice.2.9.5\build\MrAdvice.targets(14,5): error MSB3073: The command " AssemblyPath="obj\Debug x86\90\xxxxxxx.Android.dll" ReferencePath="@obj\Debug x86\90\xxxxxxx.Android.dll.MrAdvice.ReferencePath.txt" ReferenceCopyLocalPaths="@obj\Debug x86\90\xxxxxxx.Android.dll.MrAdvice.LocalReferencePath.txt" AssemblyOriginatorKeyFile="" SignAssembly=""" exited with code 9009.

This is because property MrAdviceWeaverPath is not defined. Xamarin project doesn’t have $(TargetFrameworkIdentifier) as .NETFramework or .NETCoreApp or .NETStandard.

Using net5.0\MrAdvice.Weaver.exe seems to work fine so it might be a good idea to always use that one if $(TargetFrameworkIdentifier)’ not equals to ‘.NETFramework’

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
rgroenewoudtcommented, Sep 15, 2022

It would be fine to close this bug as Xamarin is getting replaced with new .NET 6 Android and MrAdvice works well in .NET 6.

0reactions
picrapcommented, Sep 15, 2022

Thank you

Read more comments on GitHub >

github_iconTop Results From Across the Web

Xamarin Android Resource file not found
Thinking that may be part of the issue, I've changed it to "_Android" and "AndroidApp", including changing the default namespace in the project...
Read more >
"Resource" not defined in Xamarin.Android project (15.5.0 ...
This preview build seems to fix the freezing issue with Xamarin projects being cleaned that still exists in the current stable release.
Read more >
Why am I getting this error on a new Xamarin Forms ...
Done building project "ColorGames.Android.csproj" -- FAILED. The Registry is already set to allow long file paths. Xamarin.
Read more >
Unable to compile Xamarin.Android project in VS 2022 ...
I'm trying to update the Xamarin.Android app by moving the project files to a new project created with the "Android Application (Preview)" ...
Read more >
Upgrading from Xamarin.Android to net7.0-android #14598
I just tried out if that path even works, so I created an empty "Android Application" project (not an "Android App (Xamarin)"), and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found