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
The behaviour I am describing below is something that I have seen in both .net core 2.0 applications and .net standard 2.0 class libraries.
When installing the MethodBoundaryAspect.Fody package, from the UI or command line tools, the library is not immediately usable without manual package configuration. This is demonstrated below. I can not see any documentation regarding this anywhere, is this intended behaviour? Or does the 'fix' described below have any undesired side effect?
After installing the NuGet package the entry in .csproj will look as follows:
The behaviour I am describing below is something that I have seen in both .net core 2.0 applications and .net standard 2.0 class libraries.
When installing the MethodBoundaryAspect.Fody package, from the UI or command line tools, the library is not immediately usable without manual package configuration. This is demonstrated below. I can not see any documentation regarding this anywhere, is this intended behaviour? Or does the 'fix' described below have any undesired side effect?
After installing the NuGet package the entry in .csproj will look as follows:
With the package configured as follows, the library is unusable as it is not detected by the compiler - see screenshot below.
To resolve the issue I change the csproj package reference to the following and all works again.
The text was updated successfully, but these errors were encountered: