I'm a .Net developer running Windows 7 Ultimate (x64) on a 2010 MacPro (2.27Ghz/6GB RAM) using Bootcamp. Until about a month ago its been, imo, the ultimate dev workstation. However recently I've noticed that Visual Studio 2010 takes a very long time to redraw its windows. This is most noticeable when switching to it after its been in the foreground.
I don't get this problem with other Windows apps and am baffled because the machine has more than enough grunt to handle a few MDI'd windows yet grinds for up to five minutes sometimes when reactivating the VS environment - the screen update seems to slow everything down. My colleagues are using identical hardware and software but running Windows under Parallels on their Macs does not lead to this behaviour.
I'm getting desperate (and I've asked this same question at apple.stackexchange.com) - does anyone know why this might be happening and whether there's a fix ...?
Improving Performance by Changing the Visual Experience
You might have a problem with Hardware Acceleration in VS2010. I had an issue with rendering applications built using WPF because of this.
Give it a try:
http://blogs.msdn.com/b/zainnab/archive/2010/06/22/improving-performance-by-changing-the-visual-experience-vstipenv0017.aspx
And if that doesn't fix your issue, go to your video card settings (nvidia or amd) and do a "reset settings". Then try again.
Related
I am struggling to find information on this. Of course certain features such as docker and hyper-v will not function, but will Visual Studio 2017 be able to be installed and run on a Windows 10 always-connected ARM device? Like, would typical desktop/web development scenarios with .NET/C++/Python work?
Cheers.
Yes, it is possible. I just got a Asus Nova Go and tried it. Compiling and running a basic .net Core app (with an Avalonia UI) worked just fine but there are some limitations and corner cases that hopefully will get fixed.
Visual Studio takes long to launch, and when lauched is not very performant.
I think the Lenovo Yoga C630 is snappier, because of the bigger 8GB RAM and the Snapdragon 850.
If you have any further questions let me know
I've looked for an answer to this everywhere. It's not a problem with the applications I'm writing, it's a problem with the IDE itself. Whenever I try to access the dropdown menus in Visual studio like File, Edit, etc... I can't see them. I'd post a picture but new users can't. The menus will come up with some pixelated garbage that is useless.
I'm running VS2010 on a Dell Vostro 1000 running Windows 7 Ultimate 64 bit, 4GB RAM. I don't know if this is a hardware issue and I've tried re-installing several times. Same result every time.
I'm having exactly this issue and was wondering if you've managed to solve it.
My graphics drivers and display drivers are all fully up to date.
I'm on Windows 7 Ultimate 64 bit also.
I've also installed VS2012 and get a similar issue using that IDE.
I've just found this: http://connect.microsoft.com/VisualStudio/feedback/details/653315/ui-gets-messed-up
and the work around seems to fix my problem!
I logged few reports to Microsoft Forum and Microsoft Connect. However, they didn't give me an exact feedback...
I am facing trouble to read XAML file with VS2010 Workflow Designer. I already formatted twice with clean Windows 7 SP1 x64 Enterprise OS and with the KBs. So did the VS2010 SP1 Ultimate x86 with all the KBs (as well as NET4.0 KBs).
My hardware is pretty fair good with Core 2 Duo T9400 with 4GB memory size. The only drawback I believe is the display interface - Mobile Intel 4 Family Series Chipset. I have 2 colleagues using the same model like mine... They never encountered any problem with scrolling/editing the XAML inside the VS2010 WF Designer...
That is a very big question for me... Probably the only way to explain is because my hardware has problem...
Has anyone of you facing the problem like I did?
=======
HOLY COW!
FINALLY! SOLVED!
Do you know why??? If you are using HP laptop/PC, please do not install the HP ProtectTools Security Manager Suite!
This is my 3rd format with Windows 7 SP1 Enterprise x64 with default drivers installation.
The next thing I did is just installing VS2010 SP1 Ultimate x86 first.
Amazingly, XAML doesn't crash anymore!
So, I installed the driver from one to one and tested out with the VS2010 SP1.
AND FOUND THE CULPRIT!!! HP ProtectTools Security Manager Suite!
This issue has been bugging me 1 week time =.=' I never do my work whole week just to debug this issue!
It has nothing to do with Microsoft. But with VS2010SP1, it crashes with HP ProtectTools Security Manager Suite! I cannot use finger sign-in anymore :/ Sigh!
Has anyone already tried this, anything particulair that I need to be aware of?
Yep, been running it for a while and I haven't hit any problems yet. Can't say I've use it all day every day, but I've built WPF, WinForms, Web and Console apps with it for testing various things and haven't had any hitches.
I have it on my Dell X1, which is effectively my "NetBook", and it's really pretty rapid. The only glitch I have had at all is some problems with graphics acceleration, but that's down to the Intel driver I'm using being an old XP driver, and it was easily worked around.
I've been running it inside a VM in Parallels Desktop 4 on a MacBook Pro. Absolutely no problems to speak of.
(There's no sound in Windows 7 as virtualized through Parallels, which is a known issue — but not very pertinent to the operation of Visual Studio.)
Jeroen,
I've been unable to install the 2008 Team Developer edition - keep getting a permission error. I was, however, able to insall the 2008 Team Database edition. I normally install both editions, so am kind of bummed about not getting the Developer edition to install. Screenshot of the error is here if you're curious.
No Problem with team edition, but only using it for web projects.
I've been using it at work since RC1 and have not run into any issues. Have developed a WinForms app, a WebForms site and now working on a MVC project.
I have had zero problems running Visual Studio 2008 Pro on 32 bit and 64 bit editions of Windows 7 for full-time C++ development.
If the application you are developing doesn't behave correctly under UAC you may will need to run the IDE as admin otherwise it won't run correctly under debug (this is the applications problem, not Windows 7 or Visual Studios).
Others seem to have problems with access rights/permissions, this should also be fixable by running the IDE as admin (via right click) or more permanently via the compatibility tab in the shortcut properties.
I don't know why this happens, is probably related to their particular user account settings.
How stable is Visual Studio 2010 compared with VS2008 SP1 on Windows 7?
So far, VS2010 is only available as an early CTP (from last November) in a VPC, so it's not really a relevant comparison. It's for looking at, not using.
I cannot speak for VS2010 on Windows 7, but I have been using VS2008sp1 on Windows 7 as my primary development machine and it works great.
Considering I've never gotten VS2008 to crash on ANY OS, id say its hard to get any better than that. Granted I may not have put it through its full paces, but I have hit a wide range of abilities over the past year or so since moving to VS2008
EDIT:
Nevermind I just remembered crashing it when a former coworker insisted on using Source Safe, which ran off a laggy server, the lag alone brought VS2008 down.