Build .77 issues

Hi Michael!

The editing of the non-c# files exception is a silly bug. It is already
fixed, and I hope you will be able to download the build 78 shortly

--
---
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c5hduf$t4o$1@is.intellij.net...

There is now "Memory usage" in the status bar. Great! But it would help if

it said "ReSharper Memory Usage"
>

The installer is broken again (i.e. the interop assembly again could not

be located). A repair fixed that.
>

Editing inside a stored procedure is broken. Backspacing over a "(" causes

an exception to be thrown (and sent to the tracker) and entering a ")"
simply does not work (nothing appears in the editor).
>

This last one is a major pain!

>

Thanks!
-Michael

Michael,

1) Memory usage indicator: it shows the memory usage of the managed heap. I
think it is difficult / impossible to determine
what part of this memory is consumed by ReSharper.

However, unless you have other managed add-ins installed, be sure that
almost all of the memory usage can be attributed to ReSharper ;)
VS.NET itself consumes only a very modest amount of managed memory.

2) Installer: I remember you posted that in the previous build it worked OK
for you. Am I right?

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c5hduf$t4o$1@is.intellij.net...

There is now "Memory usage" in the status bar. Great! But it would help if

it said "ReSharper Memory Usage"
>

The installer is broken again (i.e. the interop assembly again could not

be located). A repair fixed that.
>

Editing inside a stored procedure is broken. Backspacing over a "(" causes

an exception to be thrown (and sent to the tracker) and entering a ")"
simply does not work (nothing appears in the editor).
>

This last one is a major pain!

>

Thanks!
-Michael

Hello Dmitry,

On memory usage: then perhaps it should say "Managed Memory Usage" because otherwise its just plain wrong (VS.NET takes up a hell of a lot more RAM than reported by this statistic).

On installer: yes, Build 76 installed over the previous version (build 75) cleanly and without any issues. Although now that I think of it, I could be wrong. I think the Cook XML library got screwed up and ReSharper wasnt able to post exception bugs on my behalf into the tracker. Still, I ran into that after the install ran without any errors.

In build 77 installer, the "unable to register..." error came back when installing over the previous build (76).

Thanks!
-Michael

Michael,

1) Memory usage indicator: it shows the memory usage of the managed
heap. I
think it is difficult / impossible to determine
what part of this memory is consumed by ReSharper.
However, unless you have other managed add-ins installed, be sure that
almost all of the memory usage can be attributed to ReSharper ;)
VS.NET itself consumes only a very modest amount of managed memory.

2) Installer: I remember you posted that in the previous build it
worked OK for you. Am I right?

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c5hduf$t4o$1@is.intellij.net...

>> There is now "Memory usage" in the status bar. Great! But it would
>> help if
>>

it said "ReSharper Memory Usage"

>> The installer is broken again (i.e. the interop assembly again could
>> not
>>

be located). A repair fixed that.

>> Editing inside a stored procedure is broken. Backspacing over a "("
>> causes
>>

an exception to be thrown (and sent to the tracker) and entering a ")"
simply does not work (nothing appears in the editor).

>> This last one is a major pain!
>>
>> Thanks!
>> -Michael