Comments on: Introducing ReSharper 5.0: Solution-Wide Warnings and Suggestions http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/ ReSharper for productivity, dotTrace for performance, dotCover for test coverage Mon, 13 Feb 2012 19:13:45 +0000 http://wordpress.org/?v=2.6.5 By: JetBrains .NET Tools Blog » Blog Archive » Introducing ReSharper 5.0: Value Tracking http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-331317 JetBrains .NET Tools Blog » Blog Archive » Introducing ReSharper 5.0: Value Tracking Sun, 10 Jul 2011 11:20:51 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-331317 [...] Solution-Wide Warnings and Suggestions [...] [...] Solution-Wide Warnings and Suggestions [...]

]]> By: JetBrains .NET Tools Blog » Blog Archive » ReSharper 5.0 Is Out! http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-312223 JetBrains .NET Tools Blog » Blog Archive » ReSharper 5.0 Is Out! Tue, 13 Apr 2010 01:32:02 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-312223 [...] Analysis: Lots of improvements, from viewing all code smells in your solution from a single tool window to upgrading foreach and for loops to LINQ queries, to value tracking and [...] [...] Analysis: Lots of improvements, from viewing all code smells in your solution from a single tool window to upgrading foreach and for loops to LINQ queries, to value tracking and [...]

]]> By: JetBrains .NET Tools Blog » Blog Archive » Introducing ReSharper 5.0: Structural Search and Replace http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-312016 JetBrains .NET Tools Blog » Blog Archive » Introducing ReSharper 5.0: Structural Search and Replace Wed, 07 Apr 2010 14:26:21 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-312016 [...] Solution-Wide Warnings and Suggestions [...] [...] Solution-Wide Warnings and Suggestions [...]

]]> By: JetBrains .NET Tools Blog » Blog Archive » Introducing ReSharper 5.0: Call Tracking http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-311991 JetBrains .NET Tools Blog » Blog Archive » Introducing ReSharper 5.0: Call Tracking Tue, 06 Apr 2010 21:58:28 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-311991 [...] Solution-Wide Warnings and Suggestions [...] [...] Solution-Wide Warnings and Suggestions [...]

]]> By: Jura Gorohovsky http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-309393 Jura Gorohovsky Fri, 19 Feb 2010 13:36:05 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-309393 @Stefan Barthel What do you mean underlining? Do you mean highlighting of errors, warnings, and suggestions in the text editor? Can you provide a screenshot? @Stefan Barthel

What do you mean underlining? Do you mean highlighting of errors, warnings, and suggestions in the text editor? Can you provide a screenshot?

]]> By: JetBrains .NET Tools Blog » Blog Archive » ReSharper 5 Beta 2 Released http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-309272 JetBrains .NET Tools Blog » Blog Archive » ReSharper 5 Beta 2 Released Wed, 17 Feb 2010 20:01:08 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-309272 [...] JetBrains .NET Tools Blog ReSharper for productivity, dotTrace for performance dotTrace Home ReSharper Home « ReSharper 5.0 Preview: Solution-Wide Warnings and Suggestions [...] [...] JetBrains .NET Tools Blog ReSharper for productivity, dotTrace for performance dotTrace Home ReSharper Home « ReSharper 5.0 Preview: Solution-Wide Warnings and Suggestions [...]

]]> By: Stefan Barthel http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-308983 Stefan Barthel Thu, 11 Feb 2010 15:40:46 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-308983 I installed the current preview on a clean VS 2010 Ultimate RC. Resharper works fine so far, unfortunately the underlining is completely missing. Any ideas what's the problem? I installed the current preview on a clean VS 2010 Ultimate RC. Resharper works fine so far, unfortunately the underlining is completely missing. Any ideas what’s the problem?

]]> By: Jura Gorohovsky http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-308498 Jura Gorohovsky Mon, 01 Feb 2010 10:51:26 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-308498 @Fabio, You can select projects to inspect in Solution Explorer one by one, thereby bypassing your test projects. @Fabio,
You can select projects to inspect in Solution Explorer one by one, thereby bypassing your test projects.

]]> By: Fabio Maulo http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-308417 Fabio Maulo Sat, 30 Jan 2010 23:56:50 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-308417 Would be very useful and option to filter projects to inspects (test projects may not need some inspection) Would be very useful and option to filter projects to inspects (test projects may not need some inspection)

]]> By: Joe White http://blogs.jetbrains.com/dotnet/2010/01/resharper-50-preview-solution-wide-warnings-and-suggestions/#comment-308259 Joe White Wed, 27 Jan 2010 16:06:51 +0000 http://blogs.jetbrains.com/dotnet/?p=404#comment-308259 @Jura, fair points -- I didn't think about the fixes that would change other files. Still, it seems like "open files" is a good first approximation. Better yet if I can tell which warnings come from which files, and can remove individual files from the inspection if they're generating too much noise -- but I could always just close the file and refresh (or re-run) the inspection. @Jura, fair points — I didn’t think about the fixes that would change other files. Still, it seems like “open files” is a good first approximation. Better yet if I can tell which warnings come from which files, and can remove individual files from the inspection if they’re generating too much noise — but I could always just close the file and refresh (or re-run) the inspection.

]]>