You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and almost works, ie. it will fix it such that VS will build and won't include the interop assembly in the manifest, however, the interface types are not 'dynamic' as they were when you included a 'reference' to an interop assembly. This causes all the method calls/property sets/gets to show 'like' errors, flagged with red squigglies, in the editor even though the build succeeds.
While the suggestion here helps:
https://github.com/NuGet/Samples/blob/main/NuGet.Samples.Interop/README.md
and almost works, ie. it will fix it such that VS will build and won't include the interop assembly in the manifest, however, the interface types are not 'dynamic' as they were when you included a 'reference' to an interop assembly. This causes all the method calls/property sets/gets to show 'like' errors, flagged with red squigglies, in the editor even though the build succeeds.
Also, seems the suggestion in:
https://github.com/NuGet/Samples/blob/main/NuGet.Samples.Interop/README.md
is not quite correct. I needed to remove this part:
AND '%(ReferencePath.NuGetPackageId)' == '$(MSBuildThisFileName)'
The text was updated successfully, but these errors were encountered: