locked
Project > Run Code Analysis on Solution - AppBuildDir not set RRS feed

  • Question

  • User126029 posted

    Xamarin Studio: 6.2 I'm trying to run code analysis on my iOS project and I get an error message:

    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets: Error: Error executing task CompileEntitlements: Required property 'AppBundleDir' not set.
    (Core.iOS) <- This is a dependent project, not the main project.

    Anyone know where I should look or where to set this 'AppBundleDir'?

    Thanks!

    Thursday, March 9, 2017 9:24 PM

Answers

  • User126029 posted

    I was fixing a warning I was getting and it somehow fixed error too.

    The warning I got was:

    All projects referencing Core.csproj must install nuget package Microsoft.Bcl.Build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317569

    To solve this, I was referencing this post: https://forums.xamarin.com/discussion/30464/microsoft-bcl-build-in-external-libraries-wont-compile

    And I put <Properties>SkipValidatePackageReferences=true</Properties> in my main csproj file where it was referencing the Core.csproj project.

    The weird thing was, it didn't get rid of this warning above but now I can Run Code Analysis on Solution. Weird.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Monday, March 13, 2017 8:37 PM

All replies

  • User126029 posted

    I was fixing a warning I was getting and it somehow fixed error too.

    The warning I got was:

    All projects referencing Core.csproj must install nuget package Microsoft.Bcl.Build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317569

    To solve this, I was referencing this post: https://forums.xamarin.com/discussion/30464/microsoft-bcl-build-in-external-libraries-wont-compile

    And I put <Properties>SkipValidatePackageReferences=true</Properties> in my main csproj file where it was referencing the Core.csproj project.

    The weird thing was, it didn't get rid of this warning above but now I can Run Code Analysis on Solution. Weird.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Monday, March 13, 2017 8:37 PM
  • User126029 posted

    Never mind, this did not fix it. The problem came back again. :(

    Monday, March 13, 2017 9:04 PM