You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
This is deliberate on their part and is an attempt to provide a single assembly to use that then has some helper assemblies.
Currently when you publish an application that has a package of this type we copy all the assemblies into the output, but then just as publish is ending we delete the assemblies that are not listed in references.
This stops the ServiceFabric.Data package, and any others that do the same thing, from working.
The text was updated successfully, but these errors were encountered:
The problem is that we use the References section to filter bothruntime and compile. To mirror NuGet 2's behavior, it should only filter compile, since the purpose of filtering out these assemblies is to avoid compiling against them, but to have them present at runtime.
The ServiceFabric.Data package (https://www.nuget.org/packages/Microsoft.ServiceFabric.Data/) contains several assemblies, only one of which is listed in the references section of the NuSpec.
This is deliberate on their part and is an attempt to provide a single assembly to use that then has some helper assemblies.
Currently when you publish an application that has a package of this type we copy all the assemblies into the output, but then just as publish is ending we delete the assemblies that are not listed in references.
This stops the ServiceFabric.Data package, and any others that do the same thing, from working.
The text was updated successfully, but these errors were encountered: