Build with VS 2017

[HeikoStudt]

For compiling, I had to make two changes and there is an issue concering one unit test:

First, I had to install NUnit TestAdapter Nuget package for supporting Visual Studio 2017. I will create a Pull Request later.

Second, I had to change the nuget.config file to contain instead of .

Third, the test "Should_convert_passed_relative_paths_to_absolute_correctly" fails always. I am not quite sure why it might have changed. It fails in VS 2015 as well.

MFG (sincerly)
HeikoStudt

[HeikoStudt]

#21 should handle the first two things. I can build with VS 2015 and VS 2017 afterwards.

I do not know, what the test expects exactly (why it does derieve the expected value like that) and why it suddenly (?) fails. Because of this I cannot help out on the third one.

MFG (sincerly)
Heiko Studt

[Yegoroff]

Absolute path should be an absolute path to the configuration file on your file system.
This test is checking that code correctly resolves relative paths to absolute ones.
You can check whether a validPath variable points to the correct path on your environment, and then try to find why the test is failing.

[HeikoStudt]

In my Debugger, I got the following values:
absolutePath = "C:\DEV\GitHub\NConfig\NConfig.Tests\bin\Debug\Configs\NConfigTest.config"
validPath = "C:\DEV\GitHub\NConfig\NConfig.Tests\bin\Debug\Debug\Configs\NConfigTest.config"
The absolutePath is correct.
So in VS 2017 (or previous?) the test runner seems to have a different AppDomain.CurrentDomain.BaseDirectory than previously. To StackOverFlows' Knowledge, in VS2010 it should point to the TestResults/out Folder instead.

MFG
HeikoStudt