Jeremy D. Miller -- The Shade Tree Developer

We were talking to the ReSharper PM yesterday in the #alt.net channel and he said to keep your eyes open for Nightly builds... they might just magically start appearing as early as Monday. :)

R# is still usable with VS 2008. Ctrl+8, minor formatting tweaks and a primary R# IntelliSense turned off make the life better.

And this situation has surely forced me to learn new tricks and R# shortcuts with it.

I'm actually not minding the wait on Martin's next book... at least right now. I haven't even finished the second Ice and Fire book :)  It will probably be awful when I actually finish the fourth, though.

Good list - Sounds like you have your priorities right  :)

This is nothing compared to my suffering in between soccer word cups :)

Ah yes, the Dark Tower - my favorite series.  The only book series that I started in high school and finally reading the final book that came out last year-ish (Sep 2006).  Not to mention that the series has been around as long as Stephen King has been writing books.

I'm purposely reading the last book slowly. :D

Man, I tried using IronRuby for the first time today, and it was _painful_.  I had very high hopes that were quickly dashed as I realized the most basic things were not implemented.

Not to mention the complete lack of designer support, which alone makes it unusable for real projects.

Right now it feels like it's going to be an eternity before IronRuby is production-ready.

Jeremy,

Well, you are not turning all R# IntelliSense off after all, just the primary one. So Ctrl+Space gives you the IS by VS with extension methods, and other features of the C# 3.5, while Ctrl+Alt+Space and Ctrl+Shift+Space keep bringing up the autocompletion of R#. Code analysis still works on case-by-case basis (although the solution-wide scan has to be shut down).

So VS 2008 with R# is still more productive than pure VS 2008 for me.

Pingback from  » Daily Bits - February 2, 2008 Alvin Ashcraft’s Daily Geek Bits: Daily links, development, gadgets and raising rugrats.

Maybe you should consider an alternate add-in to R# if you're sad about its slow release schedule; the guys @ developer express had a VS2008-compatible version of CodeRush + RefactorPro! (released products, not beta) ready right alongside VS2008 at its MSDN-subscriber RTM date (end nov-2007).

Not to start a religious war over which product is better (because I used to use R# and found R# a quite useful tool), but DevExpress' tight cooperation with Microsoft has enabled them to provide (right out of the gate) refactoring support for not only the new platform (VS2008) but all the C#3.0/VB9 language features too (oh, and did I mention their tool supports refactorings for JAVASCRIPT in the VS2008 javascript editor too? -- unbelievably clever!).

While you R# guys have been stuck in VS2005 waiting for JetBrains to get around to releasing something that works in VS2008, I've been developing (with full add-in tooling support) in the new IDE with the new language features for over two months already :)

I'm sure you're invested in your R# license, but if you're impatient to get productive in the new platform it might be worth a look @ an alternate that's better sync-ed to the VS release cycle!

Jeremy:

Good point re: the learning curve; that's definitely a non-trivial issue (as I will similarly admit that when I first picked up CodeRush it was non-trivial to become actually productive with it).  But the time-span that you would have had available to you to overcome this curve would really have been the 2.5 mos from end-nov-2007 (the VS2008 release) to mid-feb-2008 (JetBrains' projected release-date for R#4) and that's more than enough to have made the change :D

I too have often wondered about the JetBrains focus on Java tooling being either a drag (or at least a distraction) in their support/release/feature-development for R# -- its interesting that you mention its possible coupling of code/release with IntelliJ; I hadn't considered that but it does make a lot of sense on a number of levels.

I also think (personal opinion here) it may be why R# has a less-integrated-with-the-VS-IDE feel to it whereas CodeRush + RefactorPro have a much tighter integration re: user input, user feedback, etc. (most notably in the number of refactorings for which R# wants to make me step thru a series of modal dialogs and RefactorPro wants to show me the preview of my choices right within the code editor window).

In addition to familiarity with one tool vs. the other, this also represents a personal preference about how much you want to 'feel' that your add-on is a 'natural extension' of the VS IDE experience vs. clearly a separate piece of software you are launching when you want to do a refactoring.  I am a former R# user that made the switch when I changed jobs a while back and in general there is really very little that the two don't both do quite well but they definitely come at the problem of 'tooling experience' from two very different places.

Happy coding and keep up the great posts; this is one of my regular reads since I find it full of excellent real-world content~!

-Steve B.

(amazing.. you didn't mention Duke Nuk'em Forever among things that are taking too long time...)

Not a massive R# fan but it looks like from here - intellij.net/.../thread.jspa that the EAP release will be rolled out tommorow (15th Feb).

I think...

Looks like they might be ditching the Feb 15 release of the EAP in favour of nightly builds. Better than nothing I guess.

www.intellij.net/.../thread.jspa

Pingback from  www2.codebetter.com/.../resharper-4-in-2-weeks.aspx