Recently, I posted some instructions for creating an installable layout for Visual Studio 2008 Express Editions and silently installing the components that are a part of the Visual Studio 2008 Express Edition setups.
- Microsoft Visual Studio 2008 Enu Product Family Code
- Microsoft Visual Studio 2008 Enu Product Family Code Free
- Microsoft Visual Studio 2008 Enu Product Family Codes For Coupons
- Microsoft Visual Studio 2008 Enu Product Family Code 1
The Visual Studio Shell is available for Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010. It is not available for Visual Studio 2017. To access the Visual Studio Shell downloads and documentation, you must accept the Microsoft Software License Terms below. Microsoft visual studio 2008 standard free download - Microsoft Pre-release Software Visual Studio 2008 Standard Edition, Microsoft Visual Studio 2008 Service Pack 1, Microsoft Visual Studio 2005. Virus-free and 100% clean download. Get MSDN Library for Visual Studio 2008 - ENU alternative downloads. BCGSuite for MFC BCGSuite is a product that extends Visual Studio 2008/2010. Web Development. Microsoft Visual Studio 2008 SDK. Microsoft Silverlight Tools for Visual Studio 2008. Microsoft Visual Studio 2008 Shell. MsiPatch (F: vs90sp1 VS90sp1-KB945140-X64-ENU.msp) install failed on product (Microsoft Visual Studio 2008 Remote Debugger - ENU). So it says it is failing to install the VS 2008 Remote Debugger. Microsoft Visual Studio 2008 Enu Product Family Definition Escapism has it’s benefits, sure, but too much of it takes time and energy away from more productive ventures, like taking care of essentials and job searching.
In addition, there are some new silent installation command line switches introduced in the Visual Studio 2008 product family. I've heard from some customers asking me why I posted a long, involved set of instructions for silently installing the components for the Express Editions while there is a simple /q switch available for Visual Studio 2008 setup.
The good news is that since the same setup.exe chainer is used by all Visual Studio 2008 editions, these new silent switches can also be used to install the Visual Studio 2008 Express Editions. The bad news is that the Express Editions were not officially designed to support silent installations in this manner, and there is a bug that can prevent the silent install from working in some scenarios without applying one of the workarounds listed at the bottom of this post.
Description of the issue
The installers for the Express Editions assume that they are being run from a location that they have write permissions to (since the normal UI-based installation scenario starts by copying the setup files to the %temp% folder and re-launching setup from there). This means that if you create an installable layout for the VS 2008 Express Editions and then copy it to a read-only network and attempt to run setup.exe /q /norestart, setup will fail with a error message related to the setup file vs_setup.ms_.
Diagnosing the issue
The log file named %temp%dd_install_*.txt will have an error message that looks like the following:
[03/25/08,11:11:58] Microsoft Visual C# 2008 Express Edition - ENU: ***ERRORLOG EVENT*** : ERROR_FILE_NOT_FOUND/ERROR_INSTALL_PACKAGE_OPEN_FAILED returned in CRootComponent::Install for: myservermyshareVisual C# 2008 Express EditionVCSvs_setup.ms_
Microsoft Visual Studio 2008 Enu Product Family Code
Earlier in the log file, you will see the true root cause of this error:
[03/25/08,11:11:32] Microsoft Visual C# 2008 Express Edition - ENU: CreateProcess launched with cmd line: myservermyshareVisual C# 2008 Express Editionvcs..Ixpvcs.exe 'myservermyshareVisual C# 2008 Express Editionvcs..Ixpvcs.exe' /Q /X:'myservermyshareVisual C# 2008 Express EditionVCS'
[03/25/08,11:11:57] Microsoft Visual C# 2008 Express Edition - ENU: myservermyshareVisual C# 2008 Express Editionvcs..Ixpvcs.exe exited with return value: 5
Microsoft Visual Studio 2008 Enu Product Family Code Free
These log entries show that setup is attempting to extract the contents of ixpvcs.exe to the network share that setup is being run from, and it fails with return value 5 (which means access is denied, most likely because the network share is read-only).
How to work around the issue
Fortunately, there are a few options that can be used when deploying the Visual Studio 2008 Express Editions with the new /q switch in order to work around the above issue:
- Extract the contents of the main express edition setup package to the folder on the network share that hosts the setup files for the Visual Studio 2008 Express Editions.
For example, in the Visual C# 2008 Express Edition, you can do this by running ixpvcs.exe /x and selecting the path to extract the files to. When using this option, your installable layout as described in this blog post should contain both ixpvcs.exe and the files vs_setup.msi and vs_setup.cab that are inside of ixpvcs.exe in the root folder next to the file setup.exe. - Grant write permissions to the network share that hosts the setup files for the Visual Studio 2008 Express Editions
- Copy the setup files for the Visual Studio 2008 Express Edition that you want to install in silent mode to the local computer and run setup from there instead of running setup directly from the read-only network share
Putting it all together
Once you use one of the above workarounds, you can install a Visual Studio 2008 Express Edition in silent mode by running the following command line just like you can in Visual Studio 2008 Standard Edition and higher:
Microsoft Visual Studio 2008 Enu Product Family Codes For Coupons
setup.exe /q /norestart
One note - the previous blog post I wrote about the new silent switches mentioned a /full switch. This switch is not applicable to the Visual Studio 2008 Express Editions because they do not offer any selectable features that are not installed by default. So there is no need to use the /full switch during a silent install of a VS 2008 Express Edition.
I'm thinking of upgrading to Windows 10 Pro. However, I still have projects that are running in Visual Studio 2008. Due to old third-party library dependencies, I can't convert it to VS 2013 or 2015.
I have searched online, but could not find an answer. Can I run VS 2008 on Windows 10 without a problem?
Thanks!
3 Answers
I can confirm that Visual Studio 2008 works on Windows 10. I have been running it for a few months now and building large projects with it without any problems.
When I tried something similar on my Windows 10 machine, I found that I needed to reinstall all of the Visual C++ Redistributables. After that, everything worked fine.
Ben NTo expand on the comment from @Ben Voigt, the 'VSPerf Profiling control driver' used by older versions of Visual Studio is not compatible with Windows 10. Therefore to conduct any profiling activities, you either need to run your VS 2008 on Windows 7, or alternatively move to Windows 2012 or higher for Windows 2010.
Microsoft Visual Studio 2008 Enu Product Family Code 1
Source:https://blogs.msdn.microsoft.com/profiler/2012/12/10/the-visual-studio-profiler-on-windows-8/