Open RussKie opened 4 months ago
Hi @RussKie , thanks for opening this! Would
<EmbeddedFiles Condition="'$(GenerateAssemblyInfo)' == 'true'" Include="$(GeneratedAssemblyInfoFile)"/>
resolve this issue? Thanks.
Yes, that should fix the issue.
Thanks! @RussKie , I checked in the change, it should be in next release.
Great, thank you.
Hi @RussKie , thanks for opening this! Would
<EmbeddedFiles Condition="'$(GenerateAssemblyInfo)' == 'true'" Include="$(GeneratedAssemblyInfoFile)"/>
resolve this issue? Thanks.
If it will be fixed in the next release, please set the "milestone" to the next version of MSAL.NET (a milestone should already exist). It'll help partners keep track of fixes.
My question is why is it adding the generated assembly info file to embedded files in the first place? Do we know? It's good to have this fix, but what is it trying to do in the first place?
Hi @RussKie , the new version of Microsoft.Identity.Client.NativeInterop is released https://www.nuget.org/packages/Microsoft.Identity.Client.NativeInterop/0.17.0, please update to Version="0.17.0"
@xinyuxu1026 do you know the answer to my question above? thanks!
Hi @KirillOsenkov , I don't know about that.
@gladjohn might know more context.
Hi @xinyuxu1026, I followed up with @gladjohn and we both agree that the EmbeddedFiles line should just be deleted.
Instead of adding the condition, could you please just delete the whole line? Thanks!
The embedding must be conditional, otherwise it breaks the build
Repro steps:
test.csproj
```xmlClass1.cs
```cs namespace test; public class Class1 { } ```Try to compile the above - it fails because the targets unconditionally embeds non-existing non-generated assembly info: