iesi.collections | Some additional ISet & lt ; T & gt ; implementations | DevOps library

One way to solve this issue is to add a .nuget\NuGet.config file to all solutions, and set the repositoryPath to a decicated local folder.

From this link, assuming you're using VS2015:

1. Create a .nuget folder in the root of the solution (on the file system) (if you're having trouble creating a .nuget folder using windows explorer, you can do so by entering .nuget. instead)

2. Inside that folder, create a file NuGet.config.

3. In Visual Studio 2015, right click on the solution and add a new solution directory called “.nuget”

4. Right click on that folder and select to add a new an existing file and select the NuGet.config file created in (2).

5. Add content like this inside the NuGet.config file:

What is the problem? Thanks in advance!

The "Config" folder should appeared on the root of the project rather than solution.

That because NuGet team deprecated solution level packages in NuGet 3.0.

So the content files comes from nuget package should be added to the project, not the solution.

Besides, according the From a convention-based working directory:

The convention-based working directory content, Contents are copied to the project root.

The "Config" folder should appeared on the root of the project.

Update:

i have edited my question with your requests :) i'm using .NET core 2.0

Since you test project type is .net core. You should use contentFiles instead of content. content is used for packages.config. Check the Using the contentFiles element for content files and blog NuGet ContentFiles Demystified for more details.

So your .nuspec file should be:

FluentNHibernate does not support .NET Core (issue), because NHibernate has not (PR).

NHibernate PR is scheduled for v5.1, due by December 15, 2017 at the time of this writing.

mstancombe has a fork for .NET Core, but you have to build it yourself.

Remove the obj and the bin folders, some old owin dll may be left from a previous build.

I don't think this is related to NH or the fluent mappings. It sounds more like a SQL Server/SMSS issue. Have you got enough privilege to alter the data?