>> Build 216 and it kind of quiet here. >> Is it better then 215 stability wise? Does it compare to 213 in overall >> quality? >> Thank you, >> Shimon. >> >
>> Shame on you! You don't want to be a probe-unit :) :) :) >> >> 216 build is out for a few hours, so for reviews please be patient till >> tomorrow, I think >> >> -- >> Eugene Pasynkov >> Developer >> JetBrains, Inc >> http://www.jetbrains.com >> "Develop with pleasure!" >> "Shimon Sim" <shimonsim048@community.nospam> wrote in message >> news:ds8786$bof$1@is.intellij.net... >>> Build 216 and it kind of quiet here. >>> Is it better then 215 stability wise? Does it compare to 213 in overall >>> quality? >>> Thank you, >>> Shimon. >>> >> >> >
After installing 216, CPU usage is over 50% all the time. The status bar on the bottom is also constantly blinking 'More exceptions have occurred. You can continue working.' It's usable as long as your cpu can deal with running consistently above 50%. It's starting to look as though ReSharper builds are like Star Trek movies. You should skip every other one.
After installing 216, CPU usage is over 50% all the time. The status bar on the bottom is also constantly blinking 'More exceptions have occurred. You can continue working.' It's usable as long as your cpu can deal with running consistently above 50%. It's starting to look as though ReSharper builds are like Star Trek movies. You should skip every other one.
After installing 216, CPU usage is over 50% all the time. The status bar on the bottom is also constantly blinking 'More exceptions have occurred. You can continue working.' It's usable as long as your cpu can deal with running consistently above 50%. It's starting to look as though ReSharper builds are like Star Trek movies. You should skip every other one.
Everybody in ReSharper team uses our own product intensivly every day. Personally, I see exception window no more than 2-3 times per day. But our configurations and work style are nearlly the same, so we can't deliver stable and bug-free product without massive tests by our EAP users. So your opinion is very important to us.
And, also, please note that the feedback like "Build is unstable, I've uninstalled it" says nothing to us :( Please give details, so we could eliminate problems.
After installing 216, CPU usage is over 50% all the time. The status bar on the bottom is also constantly blinking 'More exceptions have occurred. You can continue working.' It's usable as long as your cpu can deal with running consistently above 50%. It's starting to look as though ReSharper builds are like Star Trek movies. You should skip every other one.
Everybody in ReSharper team uses our own product intensivly every day. Personally, I see exception window no more than 2-3 times per day. But our configurations and work style are nearlly the same, so we can't deliver stable and bug-free product without massive tests by our EAP users. So your opinion is very important to us.
And, also, please note that the feedback like "Build is unstable, I've uninstalled it" says nothing to us :( Please give details, so we could eliminate problems.
Did you ever consider asking MS to run their IDE test case suite with Resharper installed? I know of other IDE extention builders that have done so and found a lot of issues that have been fixed since.
I load my solution, and almost immediately I get exception #17153. The status bar says "More exceptions have occurred. You can continue working" and flashes madly. I get the same exception again after a few seconds, and after that the CPU stays pegged and the status bar flashes with that message until I exit VS.
>> After installing 216, CPU usage is over 50% all the time. The status bar >> on the bottom is also constantly blinking 'More exceptions have occurred. >> You can continue working.' It's usable as long as your cpu can deal with >> running consistently above 50%. It's starting to look as though >> ReSharper builds are like Star Trek movies. You should skip every other >> one. >
Eugene. You right. I am in a middle of some emergency work. Do you recommend 216 for emergency work? Shimon. "Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in message news:ds882d$ha1$1@is.intellij.net...
Shame on you! You don't want to be a probe-unit :) :) :)
>
216 build is out for a few hours, so for reviews please be patient till tomorrow, I think
Look as far as I remember by 215 there was few "complains". So right now I see improvement. I will wait till tomorrow. >
>> Build 216 and it kind of quiet here. >> Is it better then 215 stability wise? Does it compare to 213 in overall >> quality? >> Thank you, >> Shimon. >> >
I load my solution, and almost immediately I get exception #17153. The status bar says "More exceptions have occurred. You can continue working" and flashes madly. I get the same exception again after a few seconds, and after that the CPU stays pegged and the status bar flashes with that
message
until I exit VS.
This might be the same problem I had before (and had again with 216 soon after installing it). Try disabling the current line highlight, before opening any file. In my case, that 'fixes' it.
no, current line doesn't relate to this problem. By the way, have you tried to enable current line highlighting in 216? What's the problem with it now?
>> Context: >> >> I load my solution, and almost immediately I get exception #17153. >> The status bar says "More exceptions have occurred. You can continue >> working" and flashes madly. I get the same exception again after a >> few seconds, and after that the CPU stays pegged and the status bar >> flashes with that >>
message
>> until I exit VS. >>
This might be the same problem I had before (and had again with 216 soon after installing it). Try disabling the current line highlight, before opening any file. In my case, that 'fixes' it. Lionel
Hmm, looks like we're not aware of such an opportunity. Could you please provide a reference to this information?
When the refactor plugin for VB.Net 2005 was released by devexpress and microsoft they mentioned in their newsgroups that MS had run all their automated UI tests and unit tests to verify that no problems did occur. If I understood correctly these tests take 24 hours or more to run and of course provide a lot of very useful information.
I personally don't have any contacts that might help you with this, but I do know that the possibility exists.
>> Eugene Pasynkov (JetBrains) wrote: >> >>> Everybody in ReSharper team uses our own product intensivly every >>> day. Personally, I see exception window no more than 2-3 times per >>> day. But our configurations and work style are nearlly the same, so >>> we can't deliver stable and bug-free product without massive tests by >>> our EAP users. So your opinion is very important to us. >>> >>> And, also, please note that the feedback like "Build is unstable, >>> I've uninstalled it" says nothing to us :( Please give details, so we >>> could eliminate problems. >>> >> Did you ever consider asking MS to run their IDE test case suite with >> Resharper installed? I know of other IDE extention builders that have >> done so and found a lot of issues that have been fixed since. >> >> Jesse >>
>> Everybody in ReSharper team uses our own product intensivly every >> day. Personally, I see exception window no more than 2-3 times per >> day. But our configurations and work style are nearlly the same, so >> we can't deliver stable and bug-free product without massive tests by >> our EAP users. So your opinion is very important to us. >> >> And, also, please note that the feedback like "Build is unstable, >> I've uninstalled it" says nothing to us :( Please give details, so we >> could eliminate problems. >>
Did you ever consider asking MS to run their IDE test case suite with Resharper installed? I know of other IDE extention builders that have done so and found a lot of issues that have been fixed since.
no, current line doesn't relate to this problem. By the way, have you
tried
to enable current line highlighting in 216? What's the problem with it now?
I only tried it quickly yesterday at home ('fresh' installation of VS2k3 + VS2k5 from a few days ago, RS 215 being the first build installed, 216 next). After installing 216, all completion/editor options were reset, including current line highlighting (disabled by default). Everything was working fine (except for all those completion options I had to disable to let VAssist work correctly :) I enabled current line highlighting, with a file already open, and the CPU went instantly berserk when I closed the options window.
One difference with before though, this time VS2k5 wasn't responsive at all (even though it's a dual core system and the other CPU was completely free). I had to shut down VS via the task manager. Then I re-disabled current line highlighting (before opening any file :), and everything worked fine again.
I tried it right now here (at work), after installation of 216 (from 215, 'old' installation of VS2k3+2k5, the first RS build installed being... 207 or 209, I don't remember exactly). It does the same thing as before. When current line highlighting is disabled, no problem. When enabled, CPU at 100% as soon as the options window is closed and a file is opened in the editor. VS2k5 is still responsive though.
Is there something somewhere I could post/send to give more information ?
Lionel
PS: other than that, build 216 seems quite good for the moment :)
We've been using 216 on two machines all yesterday and we don't get any exceptions at all, unlike 215. In fact 216 has been so stable, with the exception of couple of minor issues, that I am going to recommend my team to upgrade to 216 if they wish to.
Minor issues: 1. Highlight current line colour seems to have been corrupted by 215 and still there in 216. It is now black on black so it is unusable. 2. 'global' keyword is not recognised but this has been documented here already.
Alex
Dan Smeltz wrote:
After installing 216, CPU usage is over 50% all the time. The status bar on the bottom is also constantly blinking 'More exceptions have occurred. You can continue working.' It's usable as long as your cpu can deal with running consistently above 50%. It's starting to look as though ReSharper builds are like Star Trek movies. You should skip every other one.
>> Context: >> >> I load my solution, and almost immediately I get exception #17153. The >> status bar says "More exceptions have occurred. You can continue working" >> and flashes madly. I get the same exception again after a few seconds, >> and >> after that the CPU stays pegged and the status bar flashes with that
message
>> until I exit VS. > > >
This might be the same problem I had before (and had again with 216 soon after installing it). Try disabling the current line highlight, before opening any file. In my case, that 'fixes' it.
I agree with this - I have the same observations (VS2003) - much more stable than 215 - no exceptions at startup. All major issues that were hampering me (mainly the double '.' and associated exception) are fixed.
I too noticed the hightlight-current line colour problem - but no problem with CPU usage. Not noticing any significant change in the memory footprint. I think I also lost the code style settings (which I think still happens every install - lost track!).
Ronnie
We've been using 216 on two machines all yesterday and we don't get any exceptions at all, unlike 215. In fact 216 has been so stable, with the exception of couple of minor issues, that I am going to recommend my team to upgrade to 216 if they wish to. Minor issues: 1. Highlight current line colour seems to have been corrupted by 215 and still there in 216. It is now black on black so it is unusable. 2. 'global' keyword is not recognised but this has been documented here already. Alex
Dan Smeltz wrote:
>> After installing 216, CPU usage is over 50% all the time. The status >> bar on the bottom is also constantly blinking 'More exceptions have >> occurred. You can continue working.' It's usable as long as your cpu >> can deal with running consistently above 50%. It's starting to look >> as though ReSharper builds are like Star Trek movies. You should >> skip every other one. >>
Shame on you! You don't want to be a probe-unit :) :) :)
216 build is out for a few hours, so for reviews please be patient till
tomorrow, I think
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Shimon Sim" <shimonsim048@community.nospam> wrote in message
news:ds8786$bof$1@is.intellij.net...
Are there any known issues with this build ? The know issues page hasn't
been updates since build 214
Gabriel Lozano-Morán
"Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in
message news:ds882d$ha1$1@is.intellij.net...
>
>
>> Build 216 and it kind of quiet here.
>> Is it better then 215 stability wise? Does it compare to 213 in overall
>> quality?
>> Thank you,
>> Shimon.
>>
>
Actually, they are the same
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Gabriel Lozano-Morán" <gabriel@no-spam.org> wrote in message
news:ds891l$nge$1@is.intellij.net...
>
>
>> Shame on you! You don't want to be a probe-unit :) :) :)
>>
>> 216 build is out for a few hours, so for reviews please be patient till
>> tomorrow, I think
>>
>> --
>> Eugene Pasynkov
>> Developer
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>> "Shimon Sim" <shimonsim048@community.nospam> wrote in message
>> news:ds8786$bof$1@is.intellij.net...
>>> Build 216 and it kind of quiet here.
>>> Is it better then 215 stability wise? Does it compare to 213 in overall
>>> quality?
>>> Thank you,
>>> Shimon.
>>>
>>
>>
>
After installing 216, CPU usage is over 50% all the time. The status bar on the bottom is also constantly blinking 'More exceptions have occurred. You can continue working.' It's usable as long as your cpu can deal with running consistently above 50%. It's starting to look as though ReSharper builds are like Star Trek movies. You should skip every other one.
I'm seeing the same thing, except that devenv is spiking my CPU. Unusable.
(I deleted everything named resharper from my source tree, too.)
Jeff
"Dan Smeltz" <no_mail@jetbrains.com> wrote in message
news:12107846.1139258083938.JavaMail.itn@is.intellij.net...
Have you posted the first occured exception to our tracker?
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Dan Smeltz" <no_mail@jetbrains.com> wrote in message
news:12107846.1139258083938.JavaMail.itn@is.intellij.net...
Everybody in ReSharper team uses our own product intensivly every day.
Personally, I see exception window no more than 2-3 times per day. But our
configurations and work style are nearlly the same, so we can't deliver
stable and bug-free product without massive tests by our EAP users. So your
opinion is very important to us.
And, also, please note that the feedback like "Build is unstable, I've
uninstalled it" says nothing to us :( Please give details, so we could
eliminate problems.
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Dan Smeltz" <no_mail@jetbrains.com> wrote in message
news:12107846.1139258083938.JavaMail.itn@is.intellij.net...
Eugene Pasynkov (JetBrains) wrote:
Did you ever consider asking MS to run their IDE test case suite with
Resharper installed? I know of other IDE extention builders that have
done so and found a lot of issues that have been fixed since.
Jesse
Context:
I load my solution, and almost immediately I get exception #17153. The
status bar says "More exceptions have occurred. You can continue working"
and flashes madly. I get the same exception again after a few seconds, and
after that the CPU stays pegged and the status bar flashes with that message
until I exit VS.
Thanks,
Jeff
"Jeff Key" <spam@sliver.com> wrote in message
news:ds8c85$a9j$1@is.intellij.net...
>
>
>> After installing 216, CPU usage is over 50% all the time. The status bar
>> on the bottom is also constantly blinking 'More exceptions have occurred.
>> You can continue working.' It's usable as long as your cpu can deal with
>> running consistently above 50%. It's starting to look as though
>> ReSharper builds are like Star Trek movies. You should skip every other
>> one.
>
Eugene.
You right. I am in a middle of some emergency work. Do you recommend 216 for
emergency work?
Shimon.
"Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in
message news:ds882d$ha1$1@is.intellij.net...
>
Look as far as I remember by 215 there was few "complains". So right now I
see improvement. I will wait till tomorrow.
>
>> Build 216 and it kind of quiet here.
>> Is it better then 215 stability wise? Does it compare to 213 in overall
>> quality?
>> Thank you,
>> Shimon.
>>
>
"Jeff Key" <spam@sliver.com> wrote in message
news:ds8esv$92s$1@is.intellij.net...
>
message
This might be the same problem I had before (and had again with 216 soon
after installing it).
Try disabling the current line highlight, before opening any file. In my
case, that 'fixes' it.
Lionel
Hello Lionel,
no, current line doesn't relate to this problem. By the way, have you tried
to enable current line highlighting in 216?
What's the problem with it now?
Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Context:
>>
>> I load my solution, and almost immediately I get exception #17153.
>> The status bar says "More exceptions have occurred. You can continue
>> working" and flashes madly. I get the same exception again after a
>> few seconds, and after that the CPU stays pegged and the status bar
>> flashes with that
>>
>> until I exit VS.
>>
Dmitry Shaporenkov (JetBrains) wrote:
When the refactor plugin for VB.Net 2005 was released by devexpress and
microsoft they mentioned in their newsgroups that MS had run all their
automated UI tests and unit tests to verify that no problems did occur.
If I understood correctly these tests take 24 hours or more to run and
of course provide a lot of very useful information.
I personally don't have any contacts that might help you with this, but
I do know that the possibility exists.
Jesse
>> Eugene Pasynkov (JetBrains) wrote:
>>
>>> Everybody in ReSharper team uses our own product intensivly every
>>> day. Personally, I see exception window no more than 2-3 times per
>>> day. But our configurations and work style are nearlly the same, so
>>> we can't deliver stable and bug-free product without massive tests by
>>> our EAP users. So your opinion is very important to us.
>>>
>>> And, also, please note that the feedback like "Build is unstable,
>>> I've uninstalled it" says nothing to us :( Please give details, so we
>>> could eliminate problems.
>>>
>> Did you ever consider asking MS to run their IDE test case suite with
>> Resharper installed? I know of other IDE extention builders that have
>> done so and found a lot of issues that have been fixed since.
>>
>> Jesse
>>
Hello Jesse,
Hmm, looks like we're not aware of such an opportunity. Could you please
provide a reference
to this information?
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Everybody in ReSharper team uses our own product intensivly every
>> day. Personally, I see exception window no more than 2-3 times per
>> day. But our configurations and work style are nearlly the same, so
>> we can't deliver stable and bug-free product without massive tests by
>> our EAP users. So your opinion is very important to us.
>>
>> And, also, please note that the feedback like "Build is unstable,
>> I've uninstalled it" says nothing to us :( Please give details, so we
>> could eliminate problems.
>>
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9fa0658c7f9f4a2bd4b11@news.intellij.net...
>
tried
I only tried it quickly yesterday at home ('fresh' installation of VS2k3 +
VS2k5 from a few days ago, RS 215 being the first build installed, 216
next). After installing 216, all completion/editor options were reset,
including current line highlighting (disabled by default). Everything was
working fine (except for all those completion options I had to disable to
let VAssist work correctly :)
I enabled current line highlighting, with a file already open, and the CPU
went instantly berserk when I closed the options window.
One difference with before though, this time VS2k5 wasn't responsive at all
(even though it's a dual core system and the other CPU was completely free).
I had to shut down VS via the task manager.
Then I re-disabled current line highlighting (before opening any file :),
and everything worked fine again.
I tried it right now here (at work), after installation of 216 (from 215,
'old' installation of VS2k3+2k5, the first RS build installed being... 207
or 209, I don't remember exactly). It does the same thing as before.
When current line highlighting is disabled, no problem. When enabled, CPU at
100% as soon as the options window is closed and a file is opened in the
editor.
VS2k5 is still responsive though.
Is there something somewhere I could post/send to give more information ?
Lionel
PS: other than that, build 216 seems quite good for the moment :)
We've been using 216 on two machines all yesterday and we don't get any
exceptions at all, unlike 215. In fact 216 has been so stable, with the
exception of couple of minor issues, that I am going to recommend my team to
upgrade to 216 if they wish to.
Minor issues:
1. Highlight current line colour seems to have been corrupted by 215 and
still there in 216. It is now black on black so it is unusable.
2. 'global' keyword is not recognised but this has been documented here already.
Alex
Dan Smeltz wrote:
Thanks, Lionel, but it was already disabled. (I'm using VS2003.)
Thanks,
Jeff
"Lionel Guilhou" <lionel.guilhou@free.fr> wrote in message
news:ds9l88$rr9$1@is.intellij.net...
>> Context:
>>
>> I load my solution, and almost immediately I get exception #17153. The
>> status bar says "More exceptions have occurred. You can continue working"
>> and flashes madly. I get the same exception again after a few seconds,
>> and
>> after that the CPU stays pegged and the status bar flashes with that
>> until I exit VS.
>
>
>
>
>
Hello Alex,
I agree with this - I have the same observations (VS2003) - much more stable
than 215 - no exceptions at startup. All major issues that were hampering
me (mainly the double '.' and associated exception) are fixed.
I too noticed the hightlight-current line colour problem - but no problem
with CPU usage. Not noticing any significant change in the memory footprint.
I think I also lost the code style settings (which I think still happens
every install - lost track!).
Ronnie
>> After installing 216, CPU usage is over 50% all the time. The status
>> bar on the bottom is also constantly blinking 'More exceptions have
>> occurred. You can continue working.' It's usable as long as your cpu
>> can deal with running consistently above 50%. It's starting to look
>> as though ReSharper builds are like Star Trek movies. You should
>> skip every other one.
>>