[219] Best EAP since 213

Hi, I'd just like to say that 219 (for me anyway) is the best release since 213. I have always reverted from since they weren't usable (throwing exceptions, freezing/crashing studio etc.). Now I can code and debug and use refactorings again. And a long awaited save works correctly for the settings.

Yes a bit slow (especially startup time), lagging a bit on the CPU but working properly. You should not forget that this is an EAP (I've seen much worse betas and release candidates from much bigger companies...). In short I can work with R# EAP much more efficient than without, (I'm counting in VS2005 as well in that statement).

I'm using it mainly on a small size project with about 2500+ files and 30 projects (around 700.000 lines of code), thick client (VS2003).

Finally - My applause for you, hard working guys, and a great open-minded company! This is a great product you're developing (& tricky one :-)!!!

/Mario Toffia

5 comments
Comment actions Permalink

I just want to take a moment to agree with you.

This is the first build I've been able to actually test for more than a
minute or two :) I'm now running with it regularly, and being very
thankful for the things that work, and doing my best to report on the things
that still need polishing.

Kudos to all on build 219!

"Mario Toffia" <no_mail@jetbrains.com> wrote in message
news:4496832.1140551027159.JavaMail.itn@is.intellij.net...

Hi, I'd just like to say that 219 (for me anyway) is the best release
since 213. I have always reverted from since they
weren't usable (throwing exceptions, freezing/crashing studio etc.). Now I
can code and debug and use refactorings again. And a long awaited save
works correctly for the settings.

>

Yes a bit slow (especially startup time), lagging a bit on the CPU but
working properly. You should not forget that this is an EAP (I've seen
much worse betas and release candidates from much bigger companies...). In
short I can work with R# EAP much more efficient than without, (I'm
counting in VS2005 as well in that statement).

>

I'm using it mainly on a small size project with about 2500+ files and 30
projects (around 700.000 lines of code), thick client (VS2003).

>

Finally - My applause for you, hard working guys, and a great open-minded
company! This is a great product you're developing (& tricky one :-)!!!

>

/Mario Toffia



0
Comment actions Permalink

Have either of you tried to debug a WinForms application with build 219 yet?
Are you using VS2005 or VS2003?

"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dtftc1$snp$1@is.intellij.net...
>I just want to take a moment to agree with you.
>

This is the first build I've been able to actually test for more than a
minute or two :) I'm now running with it regularly, and being very
thankful for the things that work, and doing my best to report on the
things that still need polishing.

>

Kudos to all on build 219!

>

"Mario Toffia" <no_mail@jetbrains.com> wrote in message
news:4496832.1140551027159.JavaMail.itn@is.intellij.net...

>> Hi, I'd just like to say that 219 (for me anyway) is the best release
>> since 213. I have always reverted from since they
>> weren't usable (throwing exceptions, freezing/crashing studio etc.). Now
>> I can code and debug and use refactorings again. And a long awaited save
>> works correctly for the settings.
>>
>> Yes a bit slow (especially startup time), lagging a bit on the CPU but
>> working properly. You should not forget that this is an EAP (I've seen
>> much worse betas and release candidates from much bigger companies...).
>> In short I can work with R# EAP much more efficient than without,
>> (I'm counting in VS2005 as well in that statement).
>>
>> I'm using it mainly on a small size project with about 2500+ files and 30
>> projects (around 700.000 lines of code), thick client (VS2003).
>>
>> Finally - My applause for you, hard working guys, and a great open-minded
>> company! This is a great product you're developing (& tricky one :-)!!!
>>
>> /Mario Toffia
>



0
Comment actions Permalink

I just ran, hit a break point, stepped around, and basically played around
with a small winforms app in debug/run mode and didn't experience any
issues.

I'm using VS2005.


"Blake Bishop" <bbishop@sorenson.com> wrote in message
news:dtg00m$rru$1@is.intellij.net...

Have either of you tried to debug a WinForms application with build 219
yet? Are you using VS2005 or VS2003?

>

"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dtftc1$snp$1@is.intellij.net...

>>I just want to take a moment to agree with you.
>>
>> This is the first build I've been able to actually test for more than a
>> minute or two :) I'm now running with it regularly, and being very
>> thankful for the things that work, and doing my best to report on the
>> things that still need polishing.
>>
>> Kudos to all on build 219!
>>
>> "Mario Toffia" <no_mail@jetbrains.com> wrote in message
>> news:4496832.1140551027159.JavaMail.itn@is.intellij.net...
>>> Hi, I'd just like to say that 219 (for me anyway) is the best release
>>> since 213. I have always reverted from since they
>>> weren't usable (throwing exceptions, freezing/crashing studio etc.). Now
>>> I can code and debug and use refactorings again. And a long awaited save
>>> works correctly for the settings.
>>>
>>> Yes a bit slow (especially startup time), lagging a bit on the CPU but
>>> working properly. You should not forget that this is an EAP (I've seen
>>> much worse betas and release candidates from much bigger companies...).
>>> In short I can work with R# EAP much more efficient than without,
>>> (I'm counting in VS2005 as well in that statement).
>>>
>>> I'm using it mainly on a small size project with about 2500+ files and
>>> 30 projects (around 700.000 lines of code), thick client (VS2003).
>>>
>>> Finally - My applause for you, hard working guys, and a great
>>> open-minded company! This is a great product you're developing (& tricky
>>> one :-)!!!
>>>
>>> /Mario Toffia
>>
>>
>



0
Comment actions Permalink

We develop ReSharper using its current version and have never experienced
problems while debugging.
Could You attach DbgCLR when Your VS hangs up and post all the stacktraces
of managed threads? It would help us to identify Your problem.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Yes, currently whitebox debugging alot and it works fine. Not in the gui at the moment though.

Cheers,
Mario

0

Please sign in to leave a comment.