VS 2017 RC

[eskech]

If using libsodium-net in a project and load it in VS 2017 RC the project cannot build. It build and run fine in VS2015 dotnet version 4.6.2 error msg: C:\temp\test1\packages\Baseclass.Contrib.Nuget.Output.2.1.0\build\net40\Baseclass.Contrib.Nuget.Output.targets(73,5): error MSB4175: The task factory "CodeTaskFactory" could not be loaded from the assembly "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Tasks.v15.0.dll". Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Tasks.v15.0.dll' or one of its dependencies. The system cannot find the file specified.

[marcbarry]

+1

If I manually switch Baseclass.Contrib.Nuget.Output from version 2.1.0 to 2.2.0-xbuild02 the project builds. This is true for versions 0.9.0 and 0.10.0 of libsodium-net.

See also https://github.com/adamcaudill/libsodium-net/issues/114

[adamcaudill]

This should be eliminated if we move ahead with #152. Handling of unmanaged DLLs in NuGet packages is far from ideal, and has lead to various issues. The use of Baseclass.Contrib.Nuget.Output is there purely to get around NuGet limitations, if #152 goes through, then it can be eliminated, which would eliminate this issue.

[Quppa]

In the meantime, can the minimum version for Baseclass.Contrib.Nuget.Output be bumped up to 2.3.0? 2.1.0 is incompatible with Visual Studio 2017 and Nuget picks the lowest version when using PackageReference (-DependencyVersion isn't supported yet). Referencing the latest Baseclass.Contrib.Nuget.Output in the project referencing libsodium-net is a workaround.

[kofarrell1076]

Any update on this. Facing the same problem as above. 2.1 is not compatible with VS2017 thanks