Hello,
I must admit, we were not very responsive in the forums for the last month
or so. We were busy developing ReSharper 4
Here is quick update.
We are currently working on preparing ReSharper for Beta - performance, memory,
overall stability and reliability. Beta should be out very soon. Then we
will have post-Beta cleanup, more stabilization for Release, fill in missing
bricks found during Beta, and then ... Well, overall time scope for ReSharper
4 release is about a month.
Thank you for your patience, we really appreciate your participation in our
early access program! We are doing our best to deliver smart and quality
product.
And while we are here, what is single most important thing you want to
be fixed/changed before release?
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
Long-term single thing: Make the f*ing logging optional. I had over 1GB of logs just yesterday.
But actually more important to me today:
I am also suffering continuous 'Unexpected Change' exceptions (however many I ignore, there's always a new one) with the latest build which isn't marked 'Do not use'. Some of these lead to existing bug reports which are either closed as 'obsolete' (clearly they're not), or as 'can't repro'.
So, short term single thing is: Provide a build which doesn't throw exceptions continuously when editing code in files it doesn't like.
I denied R# access to the folder.
Open security settings for the temp\JetLogs folder
Click Advanced
Uncheck "Inherit from parent" checkbox
Choose Remove to get a nice, empty permissions list.
As far as I can see this doesn't cause any problems except the Resharper -
Show log menu option will complain about a missing logfile ![]()
"Will Dean" <resharper@indcomp.co.uk> wrote in message
news:27201681.39981210697081931.JavaMail.jive@app4.labs.intellij.net...
Long-term single thing: Make the f*ing logging optional. I had over
1GB of logs just yesterday.
>
But actually more important to me today:
>
I am also suffering continuous 'Unexpected Change' exceptions (however
many I ignore, there's always a new one) with the latest build which isn't
marked 'Do not use'. Some of these lead to existing bug reports which
are either closed as 'obsolete' (clearly they're not), or as 'can't
repro'.
>
So, short term single thing is: Provide a build which doesn't throw
exceptions continuously when editing code in files it doesn't like.
Hello Will,
What kind of entries do you see most often? We can check if these types
of messages can be generated excessively.
WBR,
Oleg Stepanov
Senior Whiteboard Operator
JetBrains, Inc.
"Develop with pleasure!"
mailto:oleg.stepanov@jetbrains.com
Long-term single thing: Make the f*ing logging optional. I had
over 1GB of logs just yesterday.
Absolutely no offense intended, but here's how the conversation would go if you and I were standing face to face having it:
Oleg - "What kind of entries do you see most often?"
Jeremy - "Yes."
Oleg - "We can check if these types of messages can be generated excessively."
Jeremy - "At all is excessively."
I fight with enough disk access dragging down my development machines, especially in environments like the one I'm consulting in now where the machines are locked-down corp. boxes with all-file on-demand virus scanning that we cannot reconfigure. Make the logging optional. All of it.
Quite. Exactly. Absolutely.
MY COMPUTER DOES NOT BELONG TO MY SOFTWARE SUPPLIERS...
Everybody involved in writing software should remember that, always. The continuous trickle of polling and logging by every vendor's unique juxtaposition of of arrogance and incompetence is what brings PCs gradually to a halt. Even before you're wasting diskspace by the gigabyte, you're defeating power-management and washing-out caches.
The idea that anyone from JB is actually going to ask me for one of the logs is laughable. Today they've started closing recent exception bugs as duplicates of bugs which were closed as 'non repro' weeks ago.
Why not just close all the bugs and go straight for RTM?
The thing that makes optional logging an even easier thing to swallow is the fact that we're not talking about some kind of production server running completely headless with remote users who cannot be expected to re-attempt what they were doing let alone understand a problem situation and help in its diagnosis. In R#, on the other hand, I can run with logging turned off and if I do encounter a problem I just hit Undo (or at the very worst, revert a file to the version under source control). If I keep running into the same problem, then I turn on the logging so that I can report something more helpful to JetBrains.
Hello brantheman,
This was a bug which caused excessive logging in a previous build. This
should have been fixed now.
WBR,
Oleg Stepanov
Senior Whiteboard Operator
JetBrains, Inc.
"Develop with pleasure!"
mailto:oleg.stepanov@jetbrains.com
50% of my logs look like this:
8:29:27 AM.524: Thread:1: MW WM_KILLFOCUS HWND=8719578
Disposed=False. 8:29:27 AM.524: Thread:1: MW UpdateActive: HWND is
8719578.
log4net has a really neat feature with their buffering appender where you can set it to buffer debug/info messages for a certain amount and then only actually write them out to a log file when an error occurs. So if an error occurs, you get the error plus a bunch of buffered debug statements. No error, no logs.
Besides that, it would be nice if R# cleaned up the log files it created after a few days or something (perhaps it does--my folder was not that big, but it could clean it up on uninstall/reinstall).
Sam
The single most important thing I would like to see fixed is the memory leak
while editing ASPX files.
I've tried working with all the posted fixes/work arounds. I try forcing it
to "collect garbage" and while that keeps it at bay for a little while
longer the end result is always the same. I've literally watched the managed
memory monitor climb 10MB on each save of the file I'm working on till it
reaches about +300MB range and typing begins to lag behind your keystrokes.
Once you're up into the 400-500MB range, Visual Studio becomes completely
unusable, and the only fix is to restart the IDE. Now this buys time until
it does the same thing again. Some evenings I've had to restart the IDE as
much as 5 times in 2hrs just to be able to finish editing a layout in an
ASPX file. I love the product, if I didn't, I wouldn't bother working
through these things but ultimately there has to be a solution.
Here is a rundown on everything, if you want/need more, please let me know
I'll be more than happy to help get this resolved.
Visual Studio 2008 Professional
Source Gear Vault for Version Control
Resharper v4.0 - I've been working with the daily builds since day one
My C# Project:
ASP.NET (2.0) Project
49 ASPX files (The single largest ASPX file is roughly 400 lines)
148 Classes in the Business Assembly
Hardware:
Lenovo T61P
Core 2 Duo T9300 @ 2.5GHz
4GB Memory
Windows Vista Enterprise (32bit)
I never have this problem when my edits are .CS files - this is in the same
project/solution - I can work for an entire day without having the memory go
above 200MB and performance is great.
Thanks,
~Chris
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b1577bc8ca834dab6ad6f8@news.intellij.net...
Hello,
>
I must admit, we were not very responsive in the forums for the last month
or so. We were busy developing ReSharper 4
Here is quick update.
We are currently working on preparing ReSharper for Beta - performance,
memory, overall stability and reliability. Beta should be out very soon.
Then we will have post-Beta cleanup, more stabilization for Release, fill
in missing bricks found during Beta, and then ... Well, overall time scope
for ReSharper 4 release is about a month.
Thank you for your patience, we really appreciate your participation in
our early access program! We are doing our best to deliver smart and
quality product.
>
And while we are here, what is single most important thing you want to
be fixed/changed before release?
>
Sincerely,
Ilya Ryzhenkov
>
JetBrains, Inc
"Develop with pleasure!"
>
Same here, although it's not just ASPX.
VS regularly reaches 900Mb+ which is when it gets very slow. Once it gets to 1GB I start getting out of memory exceptions.
I would agree - the issue is purely one with the HTML editor. I can work
for several days when editing anything other than HTML and my memory usage
will be steady at ~200MB. As soon as I change so much as a space in the
HTML editor, memory will start inching higher, ~5MB for every 10 minutes
that I spend editing ANYTHING (not just HTML) untill I have to restart the
IDE at around ~400 - ~600MB. If I am actively changing the HTML, the memory
increase is ~10MB per minute. While in both cases, I can manually collect
the garbage; doing so will normally only release ~20MB or so.
I have tried the workaround, but there are other stablity issues with the
wrapper application. When I am using it, the overall stable of the IDE is
severly impacted, and I end up having to kill the IDE to be able to restart
it and continue working. This is normally every 20 to 40 minutes.
David
"Philip Lee" <no_reply@jetbrains.com> wrote in message
news:12553200.41941210752808741.JavaMail.jive@app4.labs.intellij.net...
Same here, although it's not just ASPX.
VS regularly reaches 900Mb+ which is when it gets very slow. Once it gets
to 1GB I start getting out of memory exceptions.
Hello Chris,
I've just submited change to fix potential memory leak in ASPX files. Due
to the complex structure of ASP support and so many variation of web site's
configurations, I'm not 100% sure it will fix problem you experience, but
please try build 801 when it is out and tell us if it helps.
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
CC> The single most important thing I would like to see fixed is the
CC> memory leak
CC> while editing ASPX files.
CC> I've tried working with all the posted fixes/work arounds. I try
CC> forcing it
CC> to "collect garbage" and while that keeps it at bay for a little
CC> while
CC> longer the end result is always the same. I've literally watched the
CC> managed
CC> memory monitor climb 10MB on each save of the file I'm working on
CC> till it
CC> reaches about +300MB range and typing begins to lag behind your
CC> keystrokes.
CC> Once you're up into the 400-500MB range, Visual Studio becomes
CC> completely
CC> unusable, and the only fix is to restart the IDE. Now this buys time
CC> until
CC> it does the same thing again. Some evenings I've had to restart the
CC> IDE as
CC> much as 5 times in 2hrs just to be able to finish editing a layout
CC> in an
CC> ASPX file. I love the product, if I didn't, I wouldn't bother
CC> working
CC> through these things but ultimately there has to be a solution.
CC> Here is a rundown on everything, if you want/need more, please let
CC> me know I'll be more than happy to help get this resolved.
CC>
CC> Visual Studio 2008 Professional
CC> Source Gear Vault for Version Control
CC> Resharper v4.0 - I've been working with the daily builds since day
CC> one
CC> My C# Project:
CC> ASP.NET (2.0) Project
CC> 49 ASPX files (The single largest ASPX file is roughly 400 lines)
CC> 148 Classes in the Business Assembly
CC> Hardware:
CC> Lenovo T61P
CC> Core 2 Duo T9300 @ 2.5GHz
CC> 4GB Memory
CC> Windows Vista Enterprise (32bit)
CC> I never have this problem when my edits are .CS files - this is in
CC> the same project/solution - I can work for an entire day without
CC> having the memory go above 200MB and performance is great.
CC>
CC> Thanks,
CC> ~Chris
CC> "Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
CC> news:76a2bd0b1577bc8ca834dab6ad6f8@news.intellij.net...
CC>
>> Hello,
>>
>> I must admit, we were not very responsive in the forums for the last
>> month
>> or so. We were busy developing ReSharper 4
Here is quick update.
>> We are currently working on preparing ReSharper for Beta -
>> performance,
>> memory, overall stability and reliability. Beta should be out very
>> soon.
>> Then we will have post-Beta cleanup, more stabilization for Release,
>> fill
>> in missing bricks found during Beta, and then ... Well, overall time
>> scope
>> for ReSharper 4 release is about a month.
>> Thank you for your patience, we really appreciate your participation
>> in
>> our early access program! We are doing our best to deliver smart and
>> quality product.
>> And while we are here, what is single most important thing you want
>> to be fixed/changed before release?
>>
>> Sincerely,
>> Ilya Ryzhenkov
>> JetBrains, Inc
>> "Develop with pleasure!"
WOW!
I downloaded build 801 this last week when I saw your msg and was amazed at
how well it performed. I of course thought maybe this was just a fluke, but
I worked with it all weekend in several projects, and had zero problems like
I saw before. I did get into it with the logger failing for some out of
memory error - but it never caused me any grief other than an annoying popup
that once I restarted went away.
Kudos to you guys, thanks for making my week! ![]()
~Chris
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b157b2a8ca84ee147f2a03@news.intellij.net...
Hello Chris,
>
I've just submited change to fix potential memory leak in ASPX files. Due
to the complex structure of ASP support and so many variation of web
site's configurations, I'm not 100% sure it will fix problem you
experience, but please try build 801 when it is out and tell us if it
helps.
Sincerely,
Ilya Ryzhenkov
>
JetBrains, Inc
"Develop with pleasure!"
I can also confirm that performance has improved considerably in build 801.
Great work, Ilya.
Mike
With auto brace completion enabled, R# frequently "steals" the brace from
the next code block when editing. This most frequently happens with
closures or object init.
Suppose I have something like:
void Foo()
{
}
Now I type in a closure
void Foo()
{
Action blah = () =>
{
//Some statements
};
}
That part works. But now I go back and remove the line }; and retype the }
void Foo()
{
Action blah = () =>
{
//Some statements
}
R# steals the next brace and uses it like this:
void Foo()
{
Action blah = () =>
{
//Some statements
};
Notice now that I have to go back and re-add the brace to end the next
block.
Please fix this. It's been in the last 10-20 nightlies... It makes editing
much more painful.
Thanks
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b1577bc8ca834dab6ad6f8@news.intellij.net...
Hello,
>
I must admit, we were not very responsive in the forums for the last month
or so. We were busy developing ReSharper 4
Here is quick update.
We are currently working on preparing ReSharper for Beta - performance,
memory, overall stability and reliability. Beta should be out very soon.
Then we will have post-Beta cleanup, more stabilization for Release, fill
in missing bricks found during Beta, and then ... Well, overall time scope
for ReSharper 4 release is about a month.
Thank you for your patience, we really appreciate your participation in
our early access program! We are doing our best to deliver smart and
quality product.
>
And while we are here, what is single most important thing you want to
be fixed/changed before release?
>
Sincerely,
Ilya Ryzhenkov
>
JetBrains, Inc
"Develop with pleasure!"
>
What i would like to be fixed is the camelhumps in the dialogs, especially the rename dialog. I find the current behaviour very frustrating.
Can you please take a look at
http://www.jetbrains.net/jira/browse/RSRP-32884
and
http://www.jetbrains.net/jira/browse/RSRP-40844
?
Thanks for the great product!
Hello alwin,
I'm afraid that most probably it will appear no earlier than in 4.0.1.
We are feature-locked now and will try to avoid major changes in behaviour
until release.
WBR,
Oleg Stepanov
Senior Whiteboard Operator
JetBrains, Inc.
"Develop with pleasure!"
mailto:oleg.stepanov@jetbrains.com
Well 4.0.1 is ok, but i hope i don't have to wait until 4.6 or 5.0... ![]()
Oh by the way, can you insert an auto property when pressing Alt+Ins in the latest builds? I can't test that here right now.
It wasn't there in +- 780 iirc.
Thanks,
Alwin
Hello,
Oh by the way, can you insert an auto property when pressing Alt+Ins
in the latest builds? I can't test that here right now.
The “Generate” functionality has been greately improved in the recent builds.
Yes, generating an auto property is a musthave feature, if you see it missing
in the latest builds in any scenarios, please tell us.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
Hello Serge,
The improved "Generate" feature is not yet public
I'm going to open it
to everyone in few days. Sorry for inconvenience.
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
SB> Hello,
SB>
>> Oh by the way, can you insert an auto property when pressing Alt+Ins
>> in the latest builds? I can't test that here right now.
>>
SB> The "Generate" functionality has been greately improved in the
SB> recent builds.
SB>
SB> Yes, generating an auto property is a musthave feature, if you see
SB> it missing in the latest builds in any scenarios, please tell us.
SB>
SB> -
SB> Serge Baltic
SB> JetBrains, Inc - http://www.jetbrains.com
SB> "Develop with pleasure!"
Please make documentation optional while installing. It is a pain in the butt to watch how R# merges documentation for a good 10 minutes.
Thanks
Hello Roman,
Yes, we will exclude documentation merging in Beta.
WBR,
Oleg Stepanov
Senior Whiteboard Operator
JetBrains, Inc.
"Develop with pleasure!"
mailto:oleg.stepanov@jetbrains.com
Please make documentation optional while installing. It is a pain in
the butt to watch how R# merges documentation for a good 10 minutes.
Biggest issue for me is formatting when entering class initializers. Sounds silly perhaps, but it affects me almost every day and requires a lot of manual reformatting and such and is the one area where I feel like ReSharper gets in my way more than it helps.
I opened a case but it's marked "won't fix" ![]()
http://www.jetbrains.net/jira/browse/RSRP-59904
Thanks,
Sam
Hello Samuel,
I have commented the issue. I'm afraid it will annoy someone if explicit
typing of "=" AFTER another "=" will be ignored. You should simply complete
the items with "=" as you do during normal text entry sequence.
WBR,
Oleg Stepanov
Senior Whiteboard Operator
JetBrains, Inc.
"Develop with pleasure!"
mailto:oleg.stepanov@jetbrains.com
Biggest issue for me is formatting when entering class initializers.
Sounds silly perhaps, but it affects me almost every day and requires
a lot of manual reformatting and such and is the one area where I feel
like ReSharper gets in my way more than it helps.
I opened a case but it's marked "won't fix"
http://www.jetbrains.net/jira/browse/RSRP-59904
Thanks,
Sam
The most important thing for me would be for ReSharper 4.0's intentions
to recognize the target framework of the project that I am working on.
Main main project is still in .Net 2.0 and that wont be changing anytime
soon, so I dont want see suggestions specific to .Net 3.5
Ilya Ryzhenkov wrote:
Hello,
I must admit, we were not very responsive in the forums for the last
month or so. We were busy developing ReSharper 4
Here is quick update.
We are currently working on preparing ReSharper for Beta - performance,
memory, overall stability and reliability. Beta should be out very soon.
Then we will have post-Beta cleanup, more stabilization for Release,
fill in missing bricks found during Beta, and then ... Well, overall
time scope for ReSharper 4 release is about a month.
Thank you for your patience, we really appreciate your participation in
our early access program! We are doing our best to deliver smart and
quality product.
And while we are here, what is single most important thing you want to
be fixed/changed before release?
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
Hello Jeff,
Select project(s), open Properties Window (View / Properties Window, F4)
and change Language Level for your project to C# 2.0.
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
JP> The most important thing for me would be for ReSharper 4.0's
JP> intentions to recognize the target framework of the project that I
JP> am working on.
JP>
JP> Main main project is still in .Net 2.0 and that wont be changing
JP> anytime soon, so I dont want see suggestions specific to .Net 3.5
JP>
JP> Ilya Ryzhenkov wrote:
JP>
>> Hello,
>>
>> I must admit, we were not very responsive in the forums for the last
>> month or so. We were busy developing ReSharper 4
Here is quick
>> update.
>> We are currently working on preparing ReSharper for Beta -
>> performance,
>> memory, overall stability and reliability. Beta should be out very
>> soon.
>> Then we will have post-Beta cleanup, more stabilization for Release,
>> fill in missing bricks found during Beta, and then ... Well, overall
>> time scope for ReSharper 4 release is about a month.
>> Thank you for your patience, we really appreciate your participation
>> in
>> our early access program! We are doing our best to deliver smart and
>> quality product.
>> And while we are here, what is single most important thing you want
>> to be fixed/changed before release?
>>
>> Sincerely,
>> Ilya Ryzhenkov
>> JetBrains, Inc
>> "Develop with pleasure!"
Hi Ilya,
That works perfectly for me, thanks. The only place it appears to be
missing is in an ASP.Net Web Application. There is no language level
setting for that type of project.
Jeff
Ilya Ryzhenkov wrote:
Hello Jeff,
Select project(s), open Properties Window (View / Properties Window, F4)
and change Language Level for your project to C# 2.0.
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
JP> The most important thing for me would be for ReSharper 4.0's
JP> intentions to recognize the target framework of the project that I
JP> am working on.
JP> JP> Main main project is still in .Net 2.0 and that wont be changing
JP> anytime soon, so I dont want see suggestions specific to .Net 3.5
JP> JP> Ilya Ryzhenkov wrote:
JP>
>>> Hello,
>>>
>>> I must admit, we were not very responsive in the forums for the last
>>> month or so. We were busy developing ReSharper 4
Here is quick
>>> update.
>>> We are currently working on preparing ReSharper for Beta -
>>> performance,
>>> memory, overall stability and reliability. Beta should be out very
>>> soon.
>>> Then we will have post-Beta cleanup, more stabilization for Release,
>>> fill in missing bricks found during Beta, and then ... Well, overall
>>> time scope for ReSharper 4 release is about a month.
>>> Thank you for your patience, we really appreciate your participation
>>> in
>>> our early access program! We are doing our best to deliver smart and
>>> quality product.
>>> And while we are here, what is single most important thing you want
>>> to be fixed/changed before release?
>>>
>>> Sincerely,
>>> Ilya Ryzhenkov
>>> JetBrains, Inc
>>> "Develop with pleasure!"
Jeff,
You can set the R# language level manually on the VS project's properties page.
It would be incorrect for R# to set the language level based on the framework version, because the C#3.0 features come from the compiler, not the framework - so you can use C#3 with .NET 2.0.
Will
We would love it if NUnit 2.4.7 support was added, specifically recognition of the RowTest attribute. As of build 799 anyway, it doesn't let you run unit tests tagged with RowTest. It would be a great help to our development if it could do this. Any chance of this?
Thanks,
Jerry
Hello Jerry,
Did you try Gallio? http://www.gallio.org/
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
IR> We would love it if NUnit 2.4.7 support was added, specifically
IR> recognition of the RowTest attribute. As of build 799 anyway, it
IR> doesn't let you run unit tests tagged with RowTest. It would be a
IR> great help to our development if it could do this. Any chance of
IR> this?
IR>
IR> Thanks,
IR> Jerry
To keep my code easy to read, I like to allign "=" in my code. I was able to make VS 2008 stop re-arranging spaces arround "=". Resharper now re-arranges my code around "=" again, making me have to go back and re-align the equal signs.
Please add an option to keep resharper from formatting spaces around equal signs so I can keep my equal signs aligned.
To keep my code easy to read, I like to align "=" in my code. I was able to make VS 2008 stop re-arranging spaces around "=". Resharper now re-arranges my code around "=" again, making me have to go back and re-align the equal signs.
Please add an option to keep resharper from formatting spaces around equal signs so I can keep my equal signs aligned.
On single thing ![]()
If i do an Alt-Ins in the Solution Explorer, then the Popup opens
everywhere, but not at the expected position (under the selected item in the
solution explorer).
I have a laptop (Monitor 1, primary, 1440x900) with an attached Display
(Monitor 2, secondary, 1680x1050).
Look at the attached picture for the position in the screen settings which
may not "normal" ![]()
Regards
Albert
Hello,
If i do an Alt-Ins in the Solution Explorer, then the Popup opens
everywhere, but not at the expected position (under the selected item
in the solution explorer).
One of the problems with Solution Explorer is that we're not told of the
selected item position onscreen.
Where would it typically appear?
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
"Serge Baltic" <baltic@intellij.net> schrieb im Newsbeitrag
news:dc0986bfd3d588ca85bec6e87728@news.intellij.net...
>> If i do an Alt-Ins in the Solution Explorer, then the Popup opens
>> everywhere, but not at the expected position (under the selected item
>> in the solution explorer).
>
One of the problems with Solution Explorer is that we're not told of the
selected item position onscreen.
>
Where would it typically appear?
Well, typically under the selected item. Within the Solution may also helps,
but not on the other side of the Window (see attachment).
Regards
Albert
The single most critical thing that needs to work in Reshaper 4.0 is website
solutions/projects.
Performance must be an order of magnitude faster than 3.1, and memory use
must be reasonable and not blow up (leak). Solutions with websites in them
must be every bit as usable and snappy as solutions with just regular C#
projects in them. That includes project/solution load time, as well as
editing speed, keystroke response, flipping from tab to tab, file to file,
and doing refactorings and using other Reshaper and VS facilities and
features.
That is absolutely critical.
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b1577bc8ca834dab6ad6f8@news.intellij.net...
Hello,
>
I must admit, we were not very responsive in the forums for the last month
or so. We were busy developing ReSharper 4
Here is quick update.
We are currently working on preparing ReSharper for Beta - performance,
memory, overall stability and reliability. Beta should be out very soon.
Then we will have post-Beta cleanup, more stabilization for Release, fill
in missing bricks found during Beta, and then ... Well, overall time scope
for ReSharper 4 release is about a month.
Thank you for your patience, we really appreciate your participation in
our early access program! We are doing our best to deliver smart and
quality product.
>
And while we are here, what is single most important thing you want to
be fixed/changed before release?
>
Sincerely,
Ilya Ryzhenkov
>
JetBrains, Inc
"Develop with pleasure!"
>
Hello Paul,
Did you try build 801 with ASP.NET projects?
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
"Develop with pleasure!"
PB> The single most critical thing that needs to work in Reshaper 4.0 is
PB> website solutions/projects.
PB>
PB> Performance must be an order of magnitude faster than 3.1, and
PB> memory use must be reasonable and not blow up (leak). Solutions
PB> with websites in them must be every bit as usable and snappy as
PB> solutions with just regular C# projects in them. That includes
PB> project/solution load time, as well as editing speed, keystroke
PB> response, flipping from tab to tab, file to file, and doing
PB> refactorings and using other Reshaper and VS facilities and
PB> features.
PB>
PB> That is absolutely critical.
PB>
PB> "Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
PB> news:76a2bd0b1577bc8ca834dab6ad6f8@news.intellij.net...
PB>
>> Hello,
>>
>> I must admit, we were not very responsive in the forums for the last
>> month
>> or so. We were busy developing ReSharper 4
Here is quick update.
>> We are currently working on preparing ReSharper for Beta -
>> performance,
>> memory, overall stability and reliability. Beta should be out very
>> soon.
>> Then we will have post-Beta cleanup, more stabilization for Release,
>> fill
>> in missing bricks found during Beta, and then ... Well, overall time
>> scope
>> for ReSharper 4 release is about a month.
>> Thank you for your patience, we really appreciate your participation
>> in
>> our early access program! We are doing our best to deliver smart and
>> quality product.
>> And while we are here, what is single most important thing you want
>> to be fixed/changed before release?
>>
>> Sincerely,
>> Ilya Ryzhenkov
>> JetBrains, Inc
>> "Develop with pleasure!"
Installed Build 803 a few hours ago and using it on a web app project. It has lots of lambda expressions and LINQ statements in it. Build 803 is MAGNITUDES faster than earlier builds! And I didn't have any problems with it so far. Superb work! ![]()
I handed off build 804 to one of our web developers, and his response was,
after two days, "It seems more stable than the 3.1.x version I was using,
but only slightly faster load times, if at all".
It's still taking several minutes for subsequent loads of a large website
project it seems. ANYTHING that can speed that up is appreciated.
I'll try to report back soon with more hard numbers, but performance with
websites still seems to be an issue, though slightly less than in 3.1.x (the
latest nightly build, not the release version).
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b157cc38ca85c2bdf0b0b0@news.intellij.net...
Hello Paul,
>
Did you try build 801 with ASP.NET projects?
>
Sincerely,
Ilya Ryzhenkov
>
JetBrains, Inc
"Develop with pleasure!"
>
>
PB> The single most critical thing that needs to work in Reshaper 4.0 is
PB> website solutions/projects.
PB> PB> Performance must be an order of magnitude faster than 3.1, and
PB> memory use must be reasonable and not blow up (leak). Solutions
PB> with websites in them must be every bit as usable and snappy as
PB> solutions with just regular C# projects in them. That includes
PB> project/solution load time, as well as editing speed, keystroke
PB> response, flipping from tab to tab, file to file, and doing
PB> refactorings and using other Reshaper and VS facilities and
PB> features.
PB> PB> That is absolutely critical.
PB> PB> "Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
PB> news:76a2bd0b1577bc8ca834dab6ad6f8@news.intellij.net...
PB>
>>> Hello,
>>>
>>> I must admit, we were not very responsive in the forums for the last
>>> month
>>> or so. We were busy developing ReSharper 4
Here is quick update.
>>> We are currently working on preparing ReSharper for Beta -
>>> performance,
>>> memory, overall stability and reliability. Beta should be out very
>>> soon.
>>> Then we will have post-Beta cleanup, more stabilization for Release,
>>> fill
>>> in missing bricks found during Beta, and then ... Well, overall time
>>> scope
>>> for ReSharper 4 release is about a month.
>>> Thank you for your patience, we really appreciate your participation
>>> in
>>> our early access program! We are doing our best to deliver smart and
>>> quality product.
>>> And while we are here, what is single most important thing you want
>>> to be fixed/changed before release?
>>>
>>> Sincerely,
>>> Ilya Ryzhenkov
>>> JetBrains, Inc
>>> "Develop with pleasure!"
>
I'd love to have XAML intellisense optionally triggered automatically just
as it is in C# code. I find it somewhat annoying having to hit Ctrl+Space
or CtrlShiftSpace every time I want to add a property (attribute)
assignment.
The one thing that would really help us is support for MSTest private accessors. See a post by Michael Flanakin on Mar 15, 2008 11:17 PM for details. It may be a bad habit to use private accessors, but we have, and all the false errors make solution-wide checking a lot less useful.
JIRA has the issue (RSRP-60958) listed as fixed, but it sure doesn't look fixed to me...
Other than that I have to say - great work!
Kevin
Edited by: Kevin Johnson on May 20, 2008 10:36 PM
Edited by: Kevin Johnson on May 20, 2008 10:39 PM
Kevin,
The one thing that would really help us is support for MSTest private
accessors. See a post by Michael Flanakin on Mar 15, 2008 11:17 PM for
details. It may be a bad habit to use private accessors, but we have, and
all the false errors make solution-wide checking a lot less useful
The support should have been implemented quite a few builds ago. Today I
just polished it a bit.
--
Sergey V. Coox
JetBrains, Inc
"Develop with pleasure!"
Please fix performance problems with ASP.NET too please. 4.0 seems better than 3.1, but any further improvement on that would be much appreciated. We have fairly large web sites and 3.x has been completely unusable on it, so we have stopped using Resharper while working with those solutions. In particular, if you can have options to exclude certain folders from being parsed, that would be good, since we have a few very large "content" folders (images, movies, etc.) and it's been very frustrating to see the "parsing xxx.jpg" message flying by the status bar, while those files have nothing to do whatsoever with the code.
Keep up the good work. W/o you guys, VS would be a pretty inferior product.