Open rikrak opened 1 year ago
Note: the referenced project is a cut-down sample for replication purposes :-)
Currently, yes if the SDK project is loaded in the same solution due to the very complicated VS internals. It will work correctly if the referenced Yardarm project is in a separate solution that was compiled separately (ProjectReference is still fine). But this is an area I'd like to improve.
Not sure if this is an environmental issue or of general concern:
I have a Yardarm SDK project that appears to correctly generate a
netstandard2.0
assembly (verified with JetBrains' DotPeek). The Yardarm project is referenced by anet7.0
Blazor project. The solution builds just fine, but Visual Studio 2022 (v17.7.0) complains about the Yardarm generated code in intellisense (lots of red-squiggle underlines). Is this expected behaviour?Replication Steps:
Class1.cs
file in theSdkConsumer
project