Software Archive
Read-only legacy content
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17060 Discussions

VS'05 slow startup after installing C++ Composer XE 2011

Mikhail_Matrosov
Novice
‎03-31-2011 07:39 AM
489 Views
Hello.

I've recently installed Intel C++ Composer XE 2011 with all integration features and after that my Visual Studio 2005 began to start really slow. Visual Studio itself without loading any project starts during about 1 min. Opening of existing project may cause delay about 2-3 mins. After opening is done all works pretty smoth as before installation of Composer. While this delay I can see fully laoded iterface and already opened source file with code but Visual Studio window is "Not responding".

Disabling integration features eliminates this delay.

Windows 7 x64, Visual Studio 2005 SP 1 (v8.0.50727.867), Intel C++ Composer XE 2011 update 5 (v2.154).
0 Kudos

Link Copied

1 Reply
reif
Beginner
‎09-26-2011 08:08 AM
489 Views
I'm seeing the same problem with Visual Studio 2008 on XP. 2 to 3 minutes to load any project and virtually no CPU usage during that time. My development machine is not on the internet. Are any of the the Composer XE 2011 components looking for new updates over the internet? If so, can this be disabled?
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.