I just started a new project in C# using Visual Studio 2012. VS2012 is up-to-date, so there is no beta or RC installed. When I run my unit tests, there is a big delay. Test summary says, that it ran 10 seconds, and the 4 unit tests ran in summary 96ms. This is what Test Explorer tells me. Why is there such a big time overhead of nearly 10 seconds? It's obviously pretty annoying if you do TDD...
Is there any configuration setting I have to set? Did I miss something?
Or is it (still) a bug in VS2012? I found a blog regarding VS2012 BETA (http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/08/what-s-new-in-visual-studio-11-beta-unit-testing.aspx). At the end of that article, they say following: "Unit Test Startup Performance – Right now we have a pretty ugly delay after you start a test run and we are aggressively working to make that go away." But I didn't find anything more about that problem. Maybe the bug is still present.
Hope someone can help me.
Thanks in advance.
In the upcoming Visual Studio quarterly release (ref http://blogs.msdn.com/b/visualstudioalm/archive/2012/10/08/visual-studio-2012-update-1-ctp.aspx), we have made some performance improvements. In short, we changed the underlying storage mechanism to improve the discovery/run time.
Please download the quarterly release when it becomes available. Also, please let us know if you have more issues.
Regards,
Patrick Tseng, Visual Studio ALM team.
Related
Is there any way to work in collaboration in Android Studio or IntelliJ?
Yes, I know about Git, but that requires pushing and pulling which is time consuming if you want to edit very small things (a single line).
Something real time would be great.
I took a look at Floobits, just not sure if we're willing to pay for something I have no idea about.
I could see that some editors like Visual Studio Code and Atom have some real-time editing solutions, but that makes running the code a bit harder.
Can someone tell me any way to achieve this?
I've already asked on jetbrain's forum, to no avail, so I'll shoot here! :)
Have anyone got resharper and visual studio 2014 ctp 3 working together? I can't live without R#! :)
If you have, how have you done it?
Cheers,
Stian
There are no plans to support VS14 with the 8.x releases (mostly because it's a CTP, and requires changes for each release, which would mean multiple releases of a compatible 8.x, which then slows us down while we're also trying to work on ReSharper 9, and also due to architectural changes in ReSharper 9 that make back porting harder). As Igal mentions, support will be there with ReSharper 9. EAPs are coming fairly soon, but there's still going to be a little wait until they're ready to start (e.g. an installer would be nice!)
I'm using TypeScript in Visual Studio 2012 and when I have to refactor my code and must temporarily introduce a lot of errors visual studio become unresponsive for up to a minute, very often, making it impossible to refactor efficiently.
How can I turn this off temporarily until I feel like I've patched the majority of errors?
It shouldn't be that bad, else it's a bug. Unfortunately with the latest release there is an issue being investigated. See https://typescript.codeplex.com/workitem/779 . If it's not this issue, then please log another describing how to reproduce the issue you are seeing reliably, and it will get investigated.
There is a fix checked in for the above issue that is being tested currently (see https://typescript.codeplex.com/SourceControl/changeset/e44dbae94e04 ). If you are feeling lucky and don't want to wait for the next update, you could always replace this line of code yourself in the typescriptServices.js file and see if it resolves your issue.
See http://blogs.msdn.com/b/typescript/archive/2013/01/29/trying-the-latest-typescript-build.aspx for details on the location of the file to update.
I'm looking for the Pex Addin for VS 2012 (or its equivalent).
I know Moles became Fakes (http://msdn.microsoft.com/en-us/library/hh549175.aspx) which is present. I want the Pex part as input generator for automated WhiteBox testing. I'm not sure how I can do this within VS2012. Could someone give me a pointer here?
The Pex Team say that they're going to build a new release of Pex, but the simultaneous move from Moles to Fakes is causing 'some changes to how things work internally, and is delaying the next release of Pex'.
One of the contributors to this question got some information from Microsoft saying that they expect the academic licence to be available in early 2013.
Finally Pex has something for Visual Studio 2012: Code Digger (http://visualstudiogallery.msdn.microsoft.com/fb5badda-4ea3-4314-a723-a1975cbdabb4). You can ask it to generate a input / output table, with parameters that will cover all your code.
However, it supports only Portable Libraries projects today... let's wait for new releases.
After upgrading to R# v6 I am unpleasantly surprised to see that the memory usage for the same application is using almost three (3) times what it did with v5.x, and is painfully slow. Not sure I would upgrade again if I had known this before hand.
Is this a known issue? Has anyone noticing the same jump been able to successfully tweak this?
Cheers,
Berryl
We're receiving mixed reports on memory and performance consumption in v6. In some cases, users call the new version a massive improvement over previous versions, other times they report increased memory consumption and lags in certain scenarios. This is pretty much the same story with every new version.
There are several known issues related to processing classic ASP files and in general processing source file on solution load. Both have been addressed lately and will be fixed in ReSharper 6.1 that is coming out later this Fall.
I suggest that you do the following:
Try to clean ReSharper caches by deleting YourSolutionName.suo and *_ReSharper.YourSolutionName* folder - this helps sometimes.
Downgrade to ReSharper 5.1.3 for the time being. This version is available via ReSharper archive.
As soon as ReSharper 6.1 comes out, install it to see if it's any better.
If it's no better, profile ReSharper and send the profile to us for investigation.
An alternative would be to profile 6.0 right away as there's a chance that your issue is something we've not yet investigated during 6.1 development.