Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Error: When using with Xamarin.Forms #72

Open
ghost opened this issue May 28, 2019 · 4 comments
Open

Build Error: When using with Xamarin.Forms #72

ghost opened this issue May 28, 2019 · 4 comments

Comments

@ghost
Copy link

ghost commented May 28, 2019

When trying to using Xamairn.Forms to create addin UI. I am getting following build error:

Error MSB4096: The item "obj/Debug/net461/_Manifest.addin.xml" in item list "EmbeddedResource" does not define a value for metadata "TargetPath". In order to use this metadata, either qualify it by specifying %(EmbeddedResource.TargetPath), or ensure that all items in this list define a value for this metadata.

This was working fine until 0.4.3 so my best guess is it is caused by this commit: dd12038#diff-bdc8ea55a71e0c73099996196023e145

Steps To Reproduce:

  1. Create a new addin project
  2. Add the following code in the csproj file:
<Target Name="DisplayMessages" BeforeTargets="BeforeCompile">
      <ItemGroup>
        <Message Include="@(EmbeddedResource)" Condition="'%(TargetPath)' != ''" />
        </ItemGroup>
 </Target>

Similar kind of code is used by Xamarin.Forms build task.

@MBrekhof
Copy link

Got the same problem just now, has this ever been solved in some way?

@matthewrdev
Copy link

matthewrdev commented Jan 22, 2020

Author of mfractor here. I strongly recommend that you do not use Xamarin.Forms to build your UIs in VS Mac; instead use XWT of AppKit. I found Xamarin.Forms caused issues in MFractors build chain and ultimately chose to remove it.

@MBrekhof Are you using Xamarin.Forms in your extension? Do you have a small sample project that triggers this error?

@MBrekhof
Copy link

Hi Matthew
Basically the error is already triggered by creating a new project/solution without any coding from me.

@praeclarum
Copy link

Just chiming in to say I would love to use Forms too and would love a solution to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants