Are there any tools which i can use to diagnose performance issues with VisualStudio 2013 Premium edition?
I'm currently running the Update2 RC (however speed has been the same prior also). and have a few extensions running
Web Essentials for Update 2 RC
Rename Visual Studio Window Title
Productivity power tools
nunit test adapter
ReadyRoll.
On an Intel Xeon E3-1220 V2 3.10GHz, machine with 8G of RAM i frequently experience performance issues which seem out of character to the resource available to Visual Studio.
The example scenario is a webforms project in a solution which references 19 other library projects, which is controlled by an in house TFS2012. Browser link is disabled, and the solution is built and deployed against the local IIS rather than IISexpress etc.
having two instances of visual studio open which have versions of the solution from different branches appears to have a large impact on performance.
switching between two instances of Visual studio can often cause a hanging state for a minute.
pasting code(even a small paragraph) ontop of code in an existing file (aspx,.vb) can cause a minute or so hang.
You did check out this page? it contains some tips from microsoft for troubleshooting performance.
You could also use i.e. process monitor from sysinternals to check what VS is actually doing in regards to file and registry access.
Another tip could be to delete this C:\Users\\AppData\Local\Temp\Temporary ASP.NET Files\
Related
I have an application written using Windows Forms and complied against Visual Studio 2010.
We recently upgraded the solution to Visual Studio 2013 and changed to using hard references to using NuGet to manage dependencies.
The application runs on a terminal server.
When running the application on the terminal server using a version compiled using 2010, it opens instantly. When running a version compiled using 2013, it takes many minutes to open.
How can I find out why the application takes so long to open the initial form?
Any thoughts or ideas about why changing these two things have made the application so slow?
Thank you.
After a lot of debugging, I found out that the MySql.Data.dll component is executing queries twice as slow as previous versions. I downgraded to version 6.3.8 in Nuget and this has increased the speed dramatically.
I hope this helps someone with similar slowness - and using the MySql component set.
I am testing web based products, and I am new to Microsoft tools. I am trying to figure out how test plan creation works, or can work depending on what configuration of Visual Studio tools I am using. I find a lot of conflicting info online.
I have the three tools below installed right now, but I can request something different if I need it. (Feel free to suggest). Any advice from pros more experienced with this tool set would be GREAT.
I access Team Foundation Server 2012 via my browser, where I can view and add product backlog items, bugs, sprints, the board etc. I cannot add test plans here, but I can add test cases to them.
I have Visual Studio 2013 installed on my PC. This seems like pretty much the same thing as the browser accessible tool, and I don't use it much because I find it easier to work from the browser for testing web.
I have Microsoft Test Manager 2012 installed on my PC. This appears to be the only place where I can create test plans, cases, and can create and utilize shared test case steps.
Questions:
How can I create test plans using the browser tool?
Is it possible to update the TFS 2012 Browser Tool to 2013, and how is that done?
Additionally to the #jessehouwing answer I would highly recommend you this free ebook:Testing for Continuous Delivery with Visual Studio 2012
Team Foundation Server 2012 update 2 adds Web Based test Case Management to TFS 2012, this is a smaller step than an upgrade to TFS 2013 all the way. You cannot just upgrade the Web Access part of a TFS installation, it would require a complete upgrade of the cluster. You also cannot just install this to your machine, it has to be installed on all the TFS servers in the cluster.
Traditionally Test Manager is the place to go to to do Test Suite Management and to view the results of a test run. Microsoft has started to move the functionality traditionally found in Test manager to the Web portal, It seems you're not the only person who found that easier to use. This transition started with TFS 2012 update 3 and was further expanded with TFS 2013.
So your options are:
Use Test Manager (you'll have to use it to manage certain things you cannot yet do on the web anyway).
Ask your Server Administrator to upgrade TFS 2012 to at least Update 2 (I'd recommend he upgrades to TFS 2012 update 4 or TFS 2013 in any case).
Ask your Server Administrator to upgrade TFS 2012 to TFS 2013.
The following resources can be very helpful in understandign how to use the tools to their fullest potential:
Visual Studio ALM Rangers' Test Guidance
Patterns & Practices' Testing for Continuous Delivery with Visual Studio 2012 (as mentioned by #Elena)
Microsoft Virtual Academy Software Testing with Visual Studio 2012 (exam 70-497 jump start)
I have written dozens of custom code analysis rules. The rules were developed targeting Visual Studio 2010. As required, the assembly has a reference to version 10.0 of FxCopSdk, Microsoft.Cci, and Microsoft.VisualStudio.CodeAnalysis. They run correctly in Visual Studio 2010 and build properly in TFS 2010.
I'd like to migrate to Visual Studio 2012. When I run the custom rules on an existing solution using VS 2012, however, I get CA0062 errors. The root cause is a CA0053 error loading the custom rules assembly. I understand that these references to the three assemblies need to be updated to version 11 for Visual Studio 2012. This can be done using version redirects in config files. I can get this to work locally by redirecting the Visual Studio 2012 IDE and FxCopCmd binaries, but am running into trouble when checking code into TFS 2010.
There are two apparent solutions we have considered, but neither is very palatable. The first is to require each developer to redirect locally, and then modify the TFS build agents to redirect as well. The second is to maintain two branches of the custom code analysis rules, one targeting version 10 (VS2010) and the other targeting version 11 (VS2012).
Is there a better way to do this, or do we need to all upgrade to TFS 2012 and Visual Studio 2012 simultaneously?
You can try to manually edit the project file and write two include blocks (one for VS2010 and one for VS2012), then define conditions to use the correct one. You only have to somehow determine if You want to build for VS2010 or VS2012 in msbuild.
Between your approaches and the one proposed by ZFE, you pretty much have all the potential candidates. Given the choices, I would strongly recommend branching since there is no official SDK for FxCop with backward-compatibility guarantees.
If you're lucky, you won't hit any behavioural or API surface changes that affect your rules, and the only difference between your two branches will be the references, so any merges will be trivial. However, any time investment you make in an alternate approach now will be lost if you need to branch later, and the likelihood of eventually needing to branch is non-negligeable.
I am looking at the possibility of installing SharePoint Foundation 2010 on my laptop so I don't have the overhead of a VM just to open a Visual Studio 2010 SharePoint project.
The only way I would do this is if I can shut down the App Pool and services. Can I have SharePoint Foundation 2010 installed but nothing running and still develop against the object model (or at least just open a freaking project)?
Thanks!
Yes you can. But you may just run a single web application and test against it while stopping all the others. I don't think it'll cause any performance issues as long as you have a decent rig.
Yes, you can. But remember the requirements to install Sharepoint Foundation 2010.
I think, if you have a machine where you can install it, so you don't need to care about overhead.
How do I disable the background compiler for Visual Basic in Visual Studio 2008?
For my sins, I have to work on a large VB.NET project and it often locks up for 20 seconds at a time whilst doing the very helpful background compilation which is extremely frustrating.
I'd rather work blind between compiles and be able to do some work.
No there is no way to disable the background compiler.
Have you installed Visual Studio 2008 SP1. There were several bugs we fixed in the RTM version of VS 2008 which can cause the IDE to hang under certain circumstances.
We take issues with the background compiler very seriously. If you can give us a repro of the problem it will definitely be investigated. If you can produce such a repro or even send us a memory dump when the IDE is locked please file a bug on Connect: https://connect.microsoft.com/VisualStudio
A couple of other steps you can take. Do you have any Add-ins installed in VS? If so try uninstalling them 1 at a time. I've seen several cases where 3rd party add-ins caused lock ups in the IDE which were completely unrelated to the C#/VB framework.