Ralf Koban
My feedback
9 results found
-
1 voteRalf Koban shared this idea ·
-
2 votes
An error occurred while saving the comment -
12 votesRalf Koban supported this idea ·
An error occurred while saving the comment Ralf Koban commentedWould be really nice, especially when used together with distributed processing.
-
2 votesRalf Koban shared this idea ·
-
1 voteRalf Koban shared this idea ·
-
4 votesRalf Koban supported this idea ·
-
6 votesRalf Koban shared this idea ·
-
4 votesRalf Koban shared this idea ·
-
3 votes
An error occurred while saving the comment Ralf Koban commentedHi Remco,
Thanks, I go for the Option to use the StyleCopEnabled property.
But I had to change $(NCrunch) to '$(NCrunch)' to get it working.<PropertyGroup>
<StyleCopEnabled Condition="'$(NCrunch)' == '1'">false</StyleCopEnabled>
</PropertyGroup>An error occurred while saving the comment Ralf Koban commentedHi Remco,
I'm not sure whether this is feasible especially for large solutions.
On one side there is already a condition on the Import.
<Import Project="..\Solution\packages\StyleCop.MSBuild.4.7.49.0\build\StyleCop.MSBuild.Targets" Condition="Exists('..\Solution\packages\StyleCop.MSBuild.4.7.49.0\build\StyleCop.MSBuild.Targets')" />On the other side, the Import is automatically added by the NuGet package, so each time we update to a new version, we need to manually adjust the condition. We have solutions with more than 160 projects, so it takes quite a long time for that adjustment (and can easily go wrong / miss something).
Are there other options already available?
Ralf Koban shared this idea ·
I think what you really want is something like NDepend.