Visual Studio 2010 + Intel i5 2500k - visual-studio-2010

Not sure if this is the right place for this, but since I know you all use VS2010...
I'm just about to pull the trigger on purchasing a bunch of new components for a new build based around an Intel i5 2500k processor. However, I came across a couple of posts that indicated that Microsoft Visual Studio 2010, when installed to a build with an i5 2500k processor would give a "processor not supported" error message and abort installation.
Considering that the bulk of my work on this machine will be done in Visual Studio 2010, this is a little concerning. Does anyone have any information on this? Or is anyone running an i5 2500k with VS2010 and no problems?
Link #1
Link #2 - See the last comment in the thread.

I've got VS 2010 installed on my machine and I run an Intel i5 2500k. No problems for me so far.

Related

Can Visual Studio 2017 be installed and used on Windows 10 on ARM (i.e. Asus NovaGo)?

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

Visual Studio 2013 and ReSharper 8 Intellisense Slow

Using Visual Studio 2013 Ultimate, and ReSharper 8.2.3 causes super laggy and slow IntelliSense responsiveness. Also, often times the dropdown is cut off and not rendered entirely, and sometimes the entire Visual Studio window turns black and becomes unresponsive for many seconds.
My system is running an NVIDIA GeForce GTX 1080 Video Card with 32 GB of RAM and an Intel Core i7-7820HK # 2.90-4.40 GHz
See the animated gif below for an example.
Anyone have similar issues and a resolution?
Are you using SSD? Secondly, try the instructions given here - https://www.jetbrains.com/help/resharper/Speeding_Up_ReSharper.html. I had the same issue that you mentioned and it was fixed by following instructions given under section - "Configuring Visual Studio preferences" in the above link. Also have a look at this update by JetBrains - >https://resharper-support.jetbrains.com/hc/en-us/articles/206546919-Visual-Studio-with-ReSharper-is-slow

VS2010 WF Designer always hang when scrolling to a bigger nest of process activities

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!

Visual Studio 2010 - Very slow display update on MacPro running Win7/Bootcamp

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.

Newly upgraded Visual Studio 2010 runs much slower than 2005

Is Visual studio 2010 slower than 2005? I just had my laptop upgraded to windows 7 64bit with visual studio 2010, and vs 2010 is much slower than vs2005 was when I had xp. Any upgrades or configurations you can think of that might help me out?
Turn off the "Enable rich client visual experience" and turn on "Use graphics hardware acceleration if available"
Extra features always come at a cost. If you don't upgrade your computer at a similar rate you upgrade your software, you'll find it gets slower and slower.
About VS2010 specifically, the UI uses WPF, so you need at least a decently passable graphics card to handle it. Intellisense also got a lot better, so it will use slightly more CPU.
For what it's worth, 2010 runs very smoothly on my computer.
Depending on your setup, Visual Studio 2010 can be faster than VS 2010 or slower. I'm not sure from your question in what way Visual Studio is running slower, though.
Is it just Visual Studio, or is anything else slower?
You mentioned you're running Windows 7 x64. If you have more than 4 GB of RAM, this is a good idea. If you have less than 4 GB, you're probably going to be slower than if you're running 32-bit. It's also worth looking at your Windows 7 performance rating--if it's low, applications like Visual Studio will be slow too.
The hardware requirements are listed over at http://www.microsoft.com/visualstudio/en-us/products/2010-editions/ultimate/system-requirements, but those are bare-bones requirements. If you're doing SharePoint development, then you'll need a much beefier system (SharePoint will compete for a lot of your system resources). I'd want at least 1 GB more RAM than recommended there even without SharePoint. The processor speed is fine for multiple cores, but if you have an old laptop 1.6 GHz and a single core won't be that fast.
Most people find an SSD drive helps incredibly.
Launching Visual Studio does seem to take longer, but to me it runs faster once it's up. F1 help is non-blocking now. Compiles can be done in parallel. Navigation and adding references is faster.
Grab the productivity power pack from vscodegallery.com--that adds a lot of shortcuts.
Visual Studio has more features than previous versions. Most people install everything. It may be better to just install the features you need.
The previous poster mentioned having a good video card or chipset. That's probably a good idea, but disk I/O and CPU are probably more important.

Resources