We've created several packages with previous versions of NuGet but since upgrading to the latest version something seems broken. We first noticed it when trying to use a C# project to bring in packages for a C++ project to overcome timing issues (the C++ supports seems to bring packages in on a background thread and often hasn't finished before the linker or compiler needs those files).
The package contains a LIB, a Win32 DLL, a header, a cpp file and some text files. We got the error '_Could not install package 'ExchLib.redist 2.30.7'. You are trying to install this package into a project that targets '.NETFramework,Version=v3.5', but the package does not contain any assembly references or content files that are compatible with that framework._'.
That surprised us because an earlier package had no C# assemblies in it either and we'd installed that without a problem using Nuget 2.4. So we tried installing that package on a new C# project and got the same error as above telling us the package contents didn't apply to the target framework.
It seems that Nuget 2.5 is trying to create .NET assembly references to DLLs and when it fails (because they aren't assemblies) it rejects the package. We've almost been able to work around the issue by adding a dummy .NET assembly to the package then using the filter so that the other files are not referenced but this just excludes all the other DLLs :-/
Comments: Hmmm. It seems related to packages created with NuGet Package Explorer. Seems like Nuget can no longer install packages created by it.
The package contains a LIB, a Win32 DLL, a header, a cpp file and some text files. We got the error '_Could not install package 'ExchLib.redist 2.30.7'. You are trying to install this package into a project that targets '.NETFramework,Version=v3.5', but the package does not contain any assembly references or content files that are compatible with that framework._'.
That surprised us because an earlier package had no C# assemblies in it either and we'd installed that without a problem using Nuget 2.4. So we tried installing that package on a new C# project and got the same error as above telling us the package contents didn't apply to the target framework.
It seems that Nuget 2.5 is trying to create .NET assembly references to DLLs and when it fails (because they aren't assemblies) it rejects the package. We've almost been able to work around the issue by adding a dummy .NET assembly to the package then using the filter so that the other files are not referenced but this just excludes all the other DLLs :-/
Comments: Hmmm. It seems related to packages created with NuGet Package Explorer. Seems like Nuget can no longer install packages created by it.