Actually both, the time it takes for Visual Studio 2005 to be responsive when started without opening a solution and the time it takes the load a big solution. I must admit I am used to it but if you haven't used ReSharper before and you are trying it out for the first time these delays will make the developer want to not give ReSharper a try.
> >> Although it has improved a lot since the early EAP's I do still find >> that there is still a lot of room for startup performance >> improvements. I have tried to convince members of my team to use >> Resharper but once they install the EAP and try it out the first thing >> they do is remove it because of the slow startup times. >> >> Gabriel Lozano-Morán >> >> "Jeff" <jeffwalsh@hotmail.com> wrote in message >> news:edrrep$8dm$1@is.intellij.net... >> >>> From the list of known issues: >>> >>> "If you open solution and then enable ReSharper, there is quite long >>> lag before ReSharper initialization progress dialog appears" >>> >>> Any idea when this will be addressed? >>> >
Actually both, the time it takes for Visual Studio 2005 to be responsive when started without opening a solution and the time it takes the load a big solution. I must admit I am used to it but if you haven't used ReSharper before and you are trying it out for the first time these delays will make the developer want to not give ReSharper a try.
> >> Although it has improved a lot since the early EAP's I do still find >> that there is still a lot of room for startup performance >> improvements. I have tried to convince members of my team to use >> Resharper but once they install the EAP and try it out the first thing >> they do is remove it because of the slow startup times. >> >> Gabriel Lozano-Morán >> >> "Jeff" <jeffwalsh@hotmail.com> wrote in message >> news:edrrep$8dm$1@is.intellij.net... >> >>> From the list of known issues: >>> >>> "If you open solution and then enable ReSharper, there is quite long >>> lag before ReSharper initialization progress dialog appears" >>> >>> Any idea when this will be addressed? >>> >
I agree, the slow startup time applies to both the time for Visual Studio to become responsive and the time to initalize ReSharper when loading the solution. Without ReSharper enabled, Visual Studio starts and is ready to go in about 1 second; With ReSharper enabled, VisualStudio is not ready for about 9 seconds after startup. It may not seem like a lot, but when you add it to the other delays associated with loading a project, it adds to the frustration.
We also have several developers who will not use ReSharper because of the slow startup times.
Actually both, the time it takes for Visual Studio 2005 to be responsive when started without opening a solution and the time it takes the load a big solution. I must admit I am used to it but if you haven't used ReSharper before and you are trying it out for the first time these delays will make the developer want to not give ReSharper a try.
Actually both, the time it takes for Visual Studio 2005 to be responsive
when started without opening a solution and the time it takes the load a big
solution. I must admit I am used to it but if you haven't used ReSharper
before and you are trying it out for the first time these delays will make
the developer want to not give ReSharper a try.
Cheers
Gabriel Lozano-Morán
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91b6d088c8a3bb569163f7@news.intellij.net...
>
>
>
>
>> Although it has improved a lot since the early EAP's I do still find
>> that there is still a lot of room for startup performance
>> improvements. I have tried to convince members of my team to use
>> Resharper but once they install the EAP and try it out the first thing
>> they do is remove it because of the slow startup times.
>>
>> Gabriel Lozano-Morán
>>
>> "Jeff" <jeffwalsh@hotmail.com> wrote in message
>> news:edrrep$8dm$1@is.intellij.net...
>>
>>> From the list of known issues:
>>>
>>> "If you open solution and then enable ReSharper, there is quite long
>>> lag before ReSharper initialization progress dialog appears"
>>>
>>> Any idea when this will be addressed?
>>>
>
Actually both, the time it takes for Visual Studio 2005 to be responsive
when started without opening a solution and the time it takes the load a big
solution. I must admit I am used to it but if you haven't used ReSharper
before and you are trying it out for the first time these delays will make
the developer want to not give ReSharper a try.
Cheers
Gabriel Lozano-Morán
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91b6d088c8a3bb569163f7@news.intellij.net...
>
>
>
>
>> Although it has improved a lot since the early EAP's I do still find
>> that there is still a lot of room for startup performance
>> improvements. I have tried to convince members of my team to use
>> Resharper but once they install the EAP and try it out the first thing
>> they do is remove it because of the slow startup times.
>>
>> Gabriel Lozano-Morán
>>
>> "Jeff" <jeffwalsh@hotmail.com> wrote in message
>> news:edrrep$8dm$1@is.intellij.net...
>>
>>> From the list of known issues:
>>>
>>> "If you open solution and then enable ReSharper, there is quite long
>>> lag before ReSharper initialization progress dialog appears"
>>>
>>> Any idea when this will be addressed?
>>>
>
I agree, the slow startup time applies to both the time for Visual Studio to
become responsive and the time to initalize ReSharper when loading the
solution.
Without ReSharper enabled, Visual Studio starts and is ready to go in about
1 second; With ReSharper enabled, VisualStudio is not ready for about 9
seconds after startup.
It may not seem like a lot, but when you add it to the other delays
associated with loading a project, it adds to the frustration.
We also have several developers who will not use ReSharper because of the
slow startup times.
"Gabriel Lozano-Morán" <gabriel.lozano@hotmail.com> wrote in message
news:ee3eef$1ef$1@is.intellij.net...
>