The ReSharper team is actively working on next version with C# 3.0 support, but we are still fixing things for ReSharper 3.0 and even add new features!
Among with various bug-fixes, ReSharper 3.0.3 features "Global Error Analysis" feature that finds compilation errors in your solution on-the-fly. It was available in early ReSharper 3.0 EAP builds, but then we decided that it is not mature enough to put it into release. Now, we've improved it and are going to include it in ReSharper 3.0.3 update.
You can get ReSharper 3.0.3 EAP build at download page. Take a look at post about Early Access Program, if you want to learn more about participating.
To enable analysis of all errors in solution, double-click a red crossing lines symbol at the very right of the status bar and check the "Analyze errors in whole solution" checkbox. Note, that it is per-solution setting. It may take quite a while to analyze your solution for the first time (you can continue your work), but once the solution has been analyzed only those files that may be affected by the changes made are reanalyzed. Tool window with all errors in your solution can be opened using ReSharper | Windows | Errors in Solution menu command. Also, next/previous error command walks through all solution errors, if solution-wide error analysis is enabled.
We would like to hear from you about this feature! Do you like it or not? Does it work fine for you? Do you have any problems? You can leave comments to this post, or drop a message in our EAP newsgroup. Thanks in advance!
Subscribe to:
Post Comments (Atom)
12 comments:
Awesome :) Keep it coming
It's great to hear that you are finally working on c# 3.0 support, wooooohoooo! :)
Do you dare to guess when the first 4.0 EAP will be available?
Thanks,
Peter
This feature sounds excellent until you consider that the current error analysis for ASP is not always accurate. Take the following for example:
asp:ObjectDataSource ID="dsJobBrokenRules" runat="server" SelectMethod="GetBrokenRules" TypeName="Eca.ElecsaMegger.WebGui.CertUploadResponse+JobBrokenRulesDataSource" ...
Resharper complains that it "Cannot resolve symbol GetBrokenRules" even when the GetBrokenRules method exists within the type declared.
If this new solution wide error analysis trips up in the same way then it will be next to useless for a solution that includes a Web application project.
Christian
This was a great feature in the early EAP versions and would be great to have it back: +faster +better, of course ;)
Sean, it is not much faster and I personally believe it well fits to small or medium projects. So that in green code you can just make a change and then just jump through errors and fix them. In large solution this won't work. Not only because Solution-wide Error analysis may take some time to analyse the code, but because such ad-hoc refactoring will simply be too large to handle. For large solutions, it's better to make classic small-step refactorings with regression tests.
Are you targeting to have ReSharper 4.0 (C# 3.0 support) released when C# 3.0 is released?
Sounds like I can skip an extra upgrade fee if I stick with ReSharper 2.5 a little longer.
good feature - but it would be much more usable with keyboard shortcut. Could you add something like "global" Alt-F12 (in IDEA/Resharper 2 style)?
So i want that in any resource i can use this shortcut to go through all the solution's errors.
vansickle,
When Solution-wide Error Analysis is enabled for solution, Goto Next/Previous Error commands (Alt+Shift+PageDown in VS key map and Alt+F12 in IDEA map) should work through solution erros. Does it work for you?
Joshua Flanagan,
We don't have release schedule available to public yet, but I can say that we are working hard to start public EAP of ReSharper 4.0 with C# 3.0 support sometime around VS2008 RTM.
This feature works nicely for me and I'm enjoying using it so far.
Does VS provide you with the means to mark files that contain errors somehow (red, squiggly underlines) in the Solution Explorer? That would be great.
Drew,
It is possible to put marks in the solution explorer, but it is currently not doable in ReSharper architecture. We are thinking about such marks, but not in the nearest future.
Ilya,
you're absolutely right, when solution-wide error analysis enabled with Alt-F12 we go through list of all errors in solution, but i think that better to have different shortcuts to go through current file errors and solution errors.
Post a Comment