R# & Server Explorer

I routinely get exceptions when openning the server explorer, and it seems
that with 211 anything to do with it is very slow. It looks like with R#,
it tries to access it, and that takes a long time.
Without R#, it works fine.


9 comments
Comment actions Permalink

Hello Ayende,

ReSharper doesn't access Server Explorer directly, but may be something
that ReSharper does causes slowdown. Could you please describe what servers
are
connected to your Server Explorer and what are you doing there when you're
observing
this problem?


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I routinely get exceptions when openning the server explorer, and it
seems
that with 211 anything to do with it is very slow. It looks like
with R#,
it tries to access it, and that takes a long time.
Without R#, it works fine.



0
Comment actions Permalink

Hello Ayende,

that's interesting, thank you a lot for information. We'll try to repeat
and fix this issue.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Two servers, one local one remote.
When I use R#, I can see that they are connected ( and it takes more
than 5
minutes to use it).
When I 'm not using R#, they are not connected until I explicitly
tells them
to.
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc19a8c7cebffce5a62c@news.intellij.net...

>> Hello Ayende,
>>
>> ReSharper doesn't access Server Explorer directly, but may be
>> something
>> that ReSharper does causes slowdown. Could you please describe what
>> servers are
>> connected to your Server Explorer and what are you doing there when
>> you're
>> observing
>> this problem?
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I routinely get exceptions when openning the server explorer, and it
>>> seems
>>> that with 211 anything to do with it is very slow. It looks like
>>> with R#,
>>> it tries to access it, and that takes a long time.
>>> Without R#, it works fine.


0
Comment actions Permalink

Two servers, one local one remote.
When I use R#, I can see that they are connected ( and it takes more than 5
minutes to use it).
When I 'm not using R#, they are not connected until I explicitly tells them
to.

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc19a8c7cebffce5a62c@news.intellij.net...

Hello Ayende,

>

ReSharper doesn't access Server Explorer directly, but may be something
that ReSharper does causes slowdown. Could you please describe what
servers are
connected to your Server Explorer and what are you doing there when you're
observing
this problem?

>
>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> I routinely get exceptions when openning the server explorer, and it
>> seems
>> that with 211 anything to do with it is very slow. It looks like
>> with R#,
>> it tries to access it, and that takes a long time.
>> Without R#, it works fine.
>



0
Comment actions Permalink

Hello Ayende,

I've played with Server Explorer & ReSharper a bit and discovered several
issues which I will fix. However,
I can't reproduce the exact problem you're talking about - that is that ReSharper
causes connection to remote
servers. Could you please tell me what project is currently opened when you're
working in the Solution Explorer?


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Two servers, one local one remote.
When I use R#, I can see that they are connected ( and it takes more
than 5
minutes to use it).
When I 'm not using R#, they are not connected until I explicitly
tells them
to.
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc19a8c7cebffce5a62c@news.intellij.net...

>> Hello Ayende,
>>
>> ReSharper doesn't access Server Explorer directly, but may be
>> something
>> that ReSharper does causes slowdown. Could you please describe what
>> servers are
>> connected to your Server Explorer and what are you doing there when
>> you're
>> observing
>> this problem?
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I routinely get exceptions when openning the server explorer, and it
>>> seems
>>> that with 211 anything to do with it is very slow. It looks like
>>> with R#,
>>> it tries to access it, and that takes a long time.
>>> Without R#, it works fine.


0
Comment actions Permalink

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc7958c7cf9e08a6d2dc@news.intellij.net...

However,
I can't reproduce the exact problem you're talking about - that is that

ReSharper

causes connection to remote
servers. Could you please tell me what project is currently opened when

you're

working in the Solution Explorer?


I've got the exact same problem, from build 209 to 212, with VS2003 and
2005.
When the Server Explorer tab first becomes active, I get several exceptions
and each connection is made, from top to bottom.

This happens even with an empty environment. Just opening VS, without any
solution, and going to the Server Explorer tab causes the problem.

In my case, all connections are on different SQL Servers in the LAN.


Lionel


0
Comment actions Permalink

Hello Lionel,

could you please point to the submitted exceptions in the tracker or post
a stack trace here?

Thanks in advance.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc7958c7cf9e08a6d2dc@news.intellij.net...

>> However,
>> I can't reproduce the exact problem you're talking about - that is
>> that

ReSharper

>> causes connection to remote
>> servers. Could you please tell me what project is currently opened
>> when

you're

>> working in the Solution Explorer?
>>

I've got the exact same problem, from build 209 to 212, with VS2003
and
2005.
When the Server Explorer tab first becomes active, I get several
exceptions
and each connection is made, from top to bottom.
This happens even with an empty environment. Just opening VS, without
any solution, and going to the Server Explorer tab causes the problem.

In my case, all connections are on different SQL Servers in the LAN.

Lionel



0
Comment actions Permalink

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc7b78c7cfa366838ed8@news.intellij.net...

Hello Lionel,

>

could you please point to the submitted exceptions in the tracker or post
a stack trace here?


Done.

I tried with 2 connections declared in the Server Explorer.
Request #12821 is for the first one.

Also, I submitted #14132 which seems to be related. It happens when closing
VS, but only if I displayed the Server Explorer before.

I forgot to indicate in the first submission that the problem does not occur
anymore once all connections have been established. Even if I close them,
switch to the Solution Explorer then back to the Server Explorer.

I haven't been able to reproduce the problem with an empty solution. Either
something changed in build 211/212 (can't remember if I saw it in 210 or
211), or I dreamed it :)


Lionel


0
Comment actions Permalink

Can't find the requests in the tracker, except for #14435 (the second
exception when closing VS).
Something wrong with the tracker or am I just on drugs ? :)


0
Comment actions Permalink

Hello Lionel,

thanks for this update - those exceptions were exactly the same we've fixed
recently. The fix will go into
213.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9cc7b78c7cfa366838ed8@news.intellij.net...

>> Hello Lionel,
>>
>> could you please point to the submitted exceptions in the tracker or
>> post a stack trace here?
>>

Done.

I tried with 2 connections declared in the Server Explorer. Request
#12821 is for the first one.

Also, I submitted #14132 which seems to be related. It happens when
closing VS, but only if I displayed the Server Explorer before.

I forgot to indicate in the first submission that the problem does not
occur anymore once all connections have been established. Even if I
close them, switch to the Solution Explorer then back to the Server
Explorer.

I haven't been able to reproduce the problem with an empty solution.
Either something changed in build 211/212 (can't remember if I saw it
in 210 or 211), or I dreamed it :)

Lionel



0

Please sign in to leave a comment.