14 February 2008

ReSharper 4 Nightly Builds - Are You Geek Enough?

-- When ReSharper 4 will be ready?
-- It is ready when it is ready!

We in ReSharper team want to make sure that C# 3.0 language is fully supported by the product. We spend a lot of time on features and look deep into details of every language quirk. You know, compilers and language standards may have very strange relationships, sometimes very weird. Still, we want to ensure maximum pleasure developing in C# 3.0 when ReSharper is ready. And it is not ready yet.

However, due to the popular demand amongst professional developers using ReSharper and C# 3.0, we are going to open nightly builds to the public. That is, not fully fledged tool, but rather our current development bits. Which could be very well broken, buggy, hanging, slow and useless at times. We will not take any responsibility if the tool wipes out all your source code! But you have a version control system in place, don't you?

So, are you geek enough to take the pill and try ReSharper 4 early builds? Read the ReSharper 4 EAP notes before you decide!

If you feel you can survive pre-release build, you can go to ReSharper 4 Nightly Builds and download your copy of ReSharper development bits.

Good luck!


Will Asrari said...

First! Just downloaded and will keep you posted!

"Are you geek enough?"

I was refreshing the EAP until midnight last night so pretty much yeah.

Fredrik said...

Wicked, will give it a go :)

Anonymous said...

Love you

Krzysztof Ko┼║mic said...

Pity that I only have 30 days to play with it :(

Ilya Ryzhenkov said...

We will renew evaluation period regulary, so all you need is use latest nightly build all the time ;)

fallout said...

Could you explain this part of the EAP notes? The way it is worded it looks like it is an update to some existing functionality, but I have no idea what it was and cannot seem to find anything about it.

External Annotations

Ability to annotate external (non-source) symbols with ReSharper-specific attributes, like CanBeNull and NotNull. Note, that we standardized attribute names for better interoperability and less configuration hassle, so you may need to refactor you code a bit if you use these attributes.