24 Replies
Last post:
Dec 4, 2007 4:20 PM by
codex897
Ilya Ryzhenkov
Hello Rick,
It seems to me there are two parts in the topic.
First, current state of ReSharper in regards of VS2008 I tried to address
in my post here: http://resharper.blogspot.com/2007/11/resharper-and-visual-studio-2008.html
Second, why do you need to use C# 3.0 right now? It is not mature enough,
it is not tested in industry, pitfalls and glitches are not known yet, there
are plenty of scepticism out there on the web and nobody really knows how
to work with it. Well, there are some marketing and other "it's so cool"
stuff on the web, but do you believe that LINQ or extension methods will
do their job better than existing solutions like ActiveRecord (http://www.castleproject.org/activerecord/index.html)
and other alternative, non-microsoft tools? We really want to know this,
honestly. There is so much buzz about how cool "var" keyword or automatic
properties are, but with ReSharper you almost don't need them 
So, could you please tell us, why do you need to use VS2008 with C# 3.0 right
now?
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
R> "codex897" <no_reply@jetbrains.com> wrote in message
R> news:21481504.1195742932129.JavaMail.itn@is.intellij.net...
R>
>> The rumours I've heard is that R# 4 is due sometime Q1 08. Given that
>> I'm about to purchase R# for the first time should I be waiting for
>> V4? If I buy now will I get hit for another licence fee in a couple
>> of months time to get the C#3.0 functionality?
>>
R> I second this request. Given that VS2008 is released, the least JB
R> can do is make their minds up about upgrade policy. I need to use
R> VS2008 right now. Why should anyone buy/upgrade to V3 now if V4 is
R> just a few months off? Answer please!
R>
Rick
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b1497ba8c9fd133e589dca@news.intellij.net...
So, could you please tell us, why do you need to use VS2008 with C# 3.0
right now?
I've been told by my employer to use VS2008 and C# 3.0. Logic and scepticism
don't feature in this argument.
Ilya Ryzhenkov
Hello Nathan,
My apologise, I didn't mean to abuse anyone. I just expressed my own opinion,
it is community newsgroup after all May be I was too much expressive...
Anyway, I'm really interested in the reasons people are so anxious about
VS2008 and C# 3.0. And more than that, I'm interested why people need it
now! It was out there for a while, in a CTP, then Beta. Release in not
something that significantly changes products like VS2008 or .NET 3.5.
For me, I have to use VS2008 and C# 3.0, so that ReSharper 4 will be good
in terms of usability, feature set and language support. If I were developing
business application, I'd wait several months while constantly monitoring
the web to understand the problems I may have when I upgrade. That's how
I would treat VS2008 release if I were on different project. On the other
hand, if I were on the hobby-project or something research-like, I'd be using
Orcas since any time it was usable to write code and do not crash too often.
For me, "RTM" mark doesn't change much.
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
IR> I really like R#, but statements like this,
IR>
IR> "Second, why do you need to use C# 3.0 right now? It is not mature
IR> enough, it is not tested in industry, pitfalls and glitches are not
IR> known yet, there are plenty of scepticism out there on the web and
IR> nobody really knows how to work with it."
IR>
IR> Make me lose respect for a company like Jetbrains. People ask if
IR> your product is going to work with the latest .NET dev tools and
IR> instead of providing a meaningful answer, you ask them why they need
IR> those tools anyway? Who are you to decide if a product is mature
IR> enough or if I need to be using it? The only scepticism[sic] I
IR> see is here.
IR>
IR> Bad form man, bad form... you don't need to be talking to customers
IR> if those are the attitudes you're going to convey.
IR>
Thanks for everyone's feedback on this. I've found it most interesting (and quite entertaining ).
So, is it safe to install the latest resharper (that's called r#?) on my vs2008 64bit computer? Are there any reports of it running smoothly with the latest release?
Thanks,
Ilya Ryzhenkov
Hello Peter,
There are problems reported with ReSharper 3, Visual Studio 2008 and x64
Windows. Those problems don't happen for every user, sometimes it runs just
fine. Sometimes, though, it crashes when you open Find Dialog (VS's one).
The problem is said to be with specific windows hooks, which we use in ReSharper.
It looks more like bug in Visual Studio, but since it is unlikely that we
can see hotfix any time soon, we are thinking of how we can fix it on our
end.
Note, that other programs which uses same hooks will cause same crashes of
VS2008. On the other hand, they didn't delay the release... 
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
IR> Thanks for everyone's feedback on this. I've found it most
IR> interesting (and quite entertaining ).
IR>
IR> So, is it safe to install the latest resharper (that's called r#?)
IR> on my vs2008 64bit computer? Are there any reports of it running
IR> smoothly with the latest release?
IR>
IR> Thanks,
IR>
Just as a quick point of feedback as to where the "now" is coming from, at least within my environment, it is that after watching so many people respond so well to beta 2 and its go-live license, but while playing it safe and waiting for RTM, those to whom we (and by we I mean dev leads like myself as well as our architect) have been talking about the upcoming features and benefits of 3.5/2008 have said "looks good, start planning the upgrade for the new year". On the other hand, had beta 2 and its go-live license not gone as well as it seems to have, we'd almost surely be waiting for SP1. To make a long story short, "now" is simply coming from the benefits we see in a move together with the perceived quality of the release. Telling us that you don't have reason to move doesn't change our needs.
PS - in case it isn't clear: we still love you guys. We'll just love you a little more when R# 4 is out. 
Here, here. R# is still my #1 development tool (aside from VS itself, without which R# is pretty worthless ), and I still have a great deal of esteem for its developers. But my normally high level of enthusiasm for the product diminishes while I can no longer use it to its full potential.
On another note, I would point out that it is quite difficult to convince the CIO to give us the go-ahead to convert all of our projects and automated builds to a new version of Visual Studio while it is still in beta. Now that the RTM is available, we will begin moving all of our solutions from VS2005 to VS2008. We will not begin targeting .NET v3.5 until Microsoft starts pushing it out to the masses via Windows Update, but in the meantime we still have the new C# 3.0 compiler, and developers like myself are anxious to start using it to its full potential. R# saps much of the joy out of this exercise, as using R# 3.x with C# 3.0 is much like driving a Porsche with a constantly flashing instrument panel and a satellite radio tuner that only receives Reggae and Weather stations.
Please, oh please throw us a bone here.