We have a big solution with many projects inside one Solution, the problem is that it hard to work with such big solution,
in some project we have big files around 50-70 KB with about 1500 lines of code, and when you try to edit this files it's very slow.
So I tried to split the big solution in smaller solutions what is partially working.
In attach you can find a sample of how I want to do the splitting
Actually the structure in sample is simple
- BigSolution.sln "something like a big project"
- SmallSolution1.sln "just some projects from BigSolution"
- SmallSolution2.sln "just some projects from BigSolution"
The problem appears on building the small solutions, as a first build I have to build the BigSolution so that all binaries are created then I open small solutions
and if Resharper is swiched OFF I have no problems, Visual Studio somehow finds the corresponding references, and Visual Studio intellisence and build works fine
And if I switch Resharper ON then in small solutions no references to projects are not found, and intellisence is not working
Now if I change the SmallSolution1.sln and SmallSolution2.sln to have only one build configuration something like "External", remove the Debug and Release configuration,
and also update all csproj to have the External as a copy of Debug.
Changing in all csproj by adding External build property and change the ProjectReferences with something like:
<ItemGroup Condition="'$(Configuration)' == 'External'">
<ItemGroup Condition="'$(Configuration)' != 'External'">
In this case when it Resharper works fine, but the big solution in Visual Studio seems to ignore the Condition and it's referecing only dll, however in big solution I have don't have at all External as a build configuration, so it should work ProjectReference and not Reference.
So is there any way to get around this, not to have the <ItemGroup Condition="'$(Configuration)' == 'External'"> but to keep the reference as a normal project so that Resharper intellisence also would work?