Hi,
i'm using your great library via NuGet but i'm facing the following issue:
if i use the library in the old package.config-format everything works as expected. But if i migrate to PackageReference-format or if i just create a new .NET Framework 4.8 console application adding the library in PackageReference-format to the .csproj file, the Liphsoft.Crypto.Argon2.dll is not copied to the bin folder and i am also not able to compile the project. I'm using a x86 configuration and i can see that the post build target works fine because the bin folder contains libargon2.dll like expected.
The correspoinding PackageReference section in the .csproj file looks like this:
<ItemGroup>
<PackageReference Include="Liphsoft.Crypto.Argon2">
<Version>1.0.5</Version>
</PackageReference>
</ItemGroup>
More info about the two formats of NuGet: https://docs.microsoft.com/en-us/nuget/consume-packages/migrate-packages-config-to-package-reference
Unfortunately i have no idea what to do since we only want to use the newer PackageReference format. Thanks for your help!
Hi,
i'm using your great library via NuGet but i'm facing the following issue:
if i use the library in the old
package.config-format everything works as expected. But if i migrate toPackageReference-format or if i just create a new.NET Framework 4.8console application adding the library inPackageReference-format to the.csprojfile, theLiphsoft.Crypto.Argon2.dllis not copied to thebinfolder and i am also not able to compile the project. I'm using ax86configuration and i can see that the post build target works fine because thebinfolder containslibargon2.dlllike expected.The correspoinding
PackageReferencesection in the.csprojfile looks like this:More info about the two formats of NuGet: https://docs.microsoft.com/en-us/nuget/consume-packages/migrate-packages-config-to-package-reference
Unfortunately i have no idea what to do since we only want to use the newer
PackageReferenceformat. Thanks for your help!