Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Suggestion: clean up the root folder

See original GitHub issue

Now we have a lot of directories in the root folder. I suggest to transform current layout to the following:

Sources for BenchmarkDotNet and BenchmarkDotNet.Diagnostics.Windows
Tests for all the test projects
Samples for all the samples projects

@adamsitnik, @mattwarren, what do you think?

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

adamsitnikcommented, Sep 20, 2016

VS should also use NuGet.config from the root solution directory.

@AndreyAkinshin Sorry, I did not know that. I have just pushed the update. 3/3 changes were possible 😉

0reactions

AndreyAkinshincommented, Sep 19, 2016

this is currently impossible because we also sign some of our test projects in order to let them use some of our internals (internalsvisibleto)

Why we can’t change the path in the corresponded project.json files? Like "keyFile": "../../src/strongNameKey.snk" instead of "keyFile": "../../strongNameKey.snk"?

this is another tricky thing. dotnet restore looks for the nuget.config in the root folder, while VS while restoring packages for the our classic projects (csproj based) looks for the Nuget folder 😉 I can try to investigate that

VS should also use NuGet.config from the root solution directory. By the way, it seems that we don’t need NuGet.targets anymore. What do you think?