VS 2010 plugin (Version 5.1.3 (build 13506))

I find the plugin for VS 2010 to really slow down Visual studio.

I find the pre-commit build feature really nice, but if it continues to slow down my visual studio so much I will need to remove it.

Any tip and trick to stop the plugin from slowing down my VS, or is it other solution for me to use pre-commit checking without the VS 2010 plugin?

\\Stian

3 comments

Hello, Stian.

I find the plugin for VS 2010 to really slow down Visual studio.

Did you try TeamCity with VS 2008, 2005? Did you faced with same problem?
Is this slow down depends on Local changes tool window activity? I mean, if Local Changes doesn't recollect your VCS changes, do your VS still slow down?

In all cases, please let me know, what version control system do you use? Also it would be greate, if you could post your TeamCity add-in logs here.
But most off all i would like to look at the result of profiling of VS 2010 with TC add-in enabled!

Any tip and trick to stop the plugin from slowing down my VS, or is it other solution for me to use pre-commit checking without the VS 2010 plugin?

You could try to use command line Remote Run tool. But that tool wouldn't commit your changes after your personal build finished.

0

It seems like it only happens when I have the "local changes" window open.
Seems like it's refreshes when I save my files. So now I just close the local changes windows and problem is gone. ;)

We use Team Foundation Server 2008.

Could it be possible to make my "local change" window only refresh manually (when I push the refresh button), or upon focus?

0

Could it be possible to make my "local change" window only refresh manually (when I push the refresh button), or upon focus?

Now there is no such option, workaround is to close Local Changes. But we plan to work on Local Changes performance is nearest future.

0

Please sign in to leave a comment.