Opened 2 years ago

Closed 2 years ago

#2871 closed defect (wontfix)

.net nuget package does not copy unmanaged dlls in legacy (4.x) asp.net web application

Reported by: jng Owned by: jng
Priority: low Milestone: 4.0
Component: Web API Version:
Severity: trivial Keywords:
Cc: External ID:

Description

I was trying to update this old legacy MVC sample

​https://github.com/jumpinjackie/mapguide-mvc-sample

Over to use the new 4.0 beta 1 netstandard2.0 nuget packages. However the unmanaged dll files that are also included with these packages are not being copied over.

Change History (2)

comment:1 by jng, 2 years ago

Summary: .net nuget package does not copy unmanaged dlls → .net nuget package does not copy unmanaged dlls in legacy (4.x) asp.net web application

comment:2 by jng, 2 years ago

Resolution: → wontfix
Status: assigned → closed

The project in question uses packages.config for tracking nuget package references.

Even in legacy .net framework projects, this is an ancient way to track nuget package references. Legacy .net projects should use the PackageReference method of tracking nuget packages. In this mode, the .targets files in our nuget packages will import properly and the native dll copying will happen.

We will not devote any further resources to trying to get these nuget packages to work in the "project using packages.config" scenario.

Note: See TracTickets for help on using tickets.