I've created a new Blazor WASM project and added to it a NuGet package from my private internal feed (let's call it
Package1 in turn depends on the
In my Blazor project, when I call methods from the
Package1 assembly, I'm getting an exception:
Could not load file or assembly 'BouncyCastle.Crypto, Version=18.104.22.168, Culture=neutral, PublicKeyToken=0e99375e54769942'. The system cannot find the file specified.
Package1's dependencies being copied locally when I build the project? As far as I can recall, this was never an issue in the old .NET Framework. Add a package to a dependent project, the package's dependencies come along with it.
Blazor1: .NET6 Blazor WASM
Package1: .NET Standard 2.0
There's nothing in Visual Studio's NuGet Package Manager options that would address this, nor is there a modern equivalent to the old
CopyLocal setting in the reference's properties sheet.
How can I get
Package1's dependencies copied locally without adding