![]() NET 4.7.1 version and remove the extra NuGet assembly. In fact, if I do add NuGet package assembly, I now have two assemblies having the namespace - one in and another in - hence the reference problem. No longer is it required to add a NuGet assembly. NET 4.7.1, the namespace is found in the assembly. The NuGet packages were in conflict with the native. NET has many of these NuGet assemblies added to standard libraries. When changing to VS2017 we elected to upgrade. This particular project was originally developed in VS2015 using. The NuGet install process appears to have completed with no errors, but still I am left with an invalid reference. I created a brand new VS2017 WebApi project referencing. ![]() Has anyone else experienced this problem, and/or has anyone any suggestions on why this is occurring and what should be done to facilitate a fix? I am thinking of rebuilding it from scratch in VS2017 to try to identify the problem. csproj file nothing out of the ordinary is jumping out. but other NuGet references are found with no problem. When opening in Visual Studio 2017 several but not all NuGet package references are not found and compile fails. When opening in Visual Studio 2015 all references are found and project builds successfully. I have a solution with two projects - a primary project, and a unit test project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |