I have old source that needs to be compiled on VC 6 C++ version.
For that I run a Windows 2008 (32bit) virtual machine and installed the 2003 platform SDK.
I wanted to make a new machine running windows 2008 R2 and therefor it is Windows SDK for Windows Server 2008 and .NET Framework 3.5 available to install.
So here is the question: Does this platform SDK include the old includes, header files and libs so I can compile the sources or is that not possible at all?
Tho I can't install the 2003 platform SDK on the 2008 R2 machine (at least the default setup won't let me do it).
Just for everyone to know asking the same: I had no problem installing VC++ 6 on a Win2k8 R2 even with warnings. Moved all SDK Files to the machine as well and manually setup all the include, libs, app pathes in the correct sort order I had on the other machine.
Compiled all components without a problem. So finally it seems it works even with some stress-calls from the setup program that there is no support for this.
Related
I've installed VS 2017 on Windows 7 machine and built the C++ project targeting 8.1 SDK, but the binaries are not starting on windows 7. The same works on Windows server 2016 and Windows 10 OS.
I had checked VC 2015 runtime is installed on both the windows server and windows 7 machine. And windows 8.1 SDK (as part of VS 2015?) is installed on my local machine running on Windows 7. Previously, I had Visual studio 2015 installed and the binaries used to work fine both on windows 7 and windows server.
I am not sure if the runtime dlls in windows\system32 are corrupted or changed due to VS 2017 installation.
PS: I noticed the same issue of exe not starting when running the newly installed firefox which comes with C-runtime dlls packed.
The problem turned out to be due to the use of the instruction set (AVX2) used by the dependency project, that wasn't available in the windows machine.
I have Visual Studio 2013 running on Windows 7 Pro. I needed the Windows Driver Kit for a project so I downloaded and installed this WDK 8.1 Update (for Windows 8.1, 8, and 7 drivers).
In this case I had not installed components such as the Windows Driver Kit Version 7.1.0 before installing WDK 8.1 Update.
Now I do not see the build environments created anywhere so I am not sure if this version of WDK requires either an earlier version of WDK as well, if something went wrong during installation, or if Microsoft made changes to the build environments.
However, when I had the aforementioned Windows Driver Kit Version 7.1.0 installed on another machine, it had created the build environments shown below.
Should the WDK 8.1 Update be sufficient on its own to create the build environments and if so, where can they be accessed?
Starting with Window 8 all tools (Debugger, Windows performance Tools, ADK, WDK) are installed under C:\Program Files (x86)\Windows Kits\VERSION and can be found under Windows Kits in the startmenu. Look a bit under your current position to access the Windows Kits folder.
i can't find this information anywhere. I know that if you install vs2010 express on a 32bit os you need the win7 sdk to build 64 bit, but is it the same the other way round?
EDIT - I am interested in the c++ version, but I guess it's probably the same for others
thanks
oli
By default VS2010 Express will only target Win32. It doesn't matter if you are running Win7-64, MSVC++ Express uses the 32-bit tools unless you install the SDK.
From MSDN:
64-bit tools are not available on Visual C++ Express by default. To enable 64-bit tools on Visual C++ Express, install the Windows Software Development Kit (SDK) in addition to Visual C++ Express.
I have been able to successfully build and deploy C# apps from a Win 7 64bit machine onto machines running 32 bit Windows XP, Vista and Win 7 without any extra SDK. So far I have had no issues.
Regards
AJ
I have a Windows 7 machine with Visual Studio 2005 SP1 installed. Using this, I build an application which loads a DLL at runtime compiled with VS2005 SP1 but on Windows XP. This fails, with the following error:
"...\foo.dll": The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
The DLL loaded is compiled against the debug CRT. The answer to this question hints that vcredist_x86.exe only contains release-versions of the CRT. I'm not sure if that is relevant in this case, since both my machine and the machine on which the DLL was compiled on both have the full VS2005 SP1 installed.
Should I attempt to rebuild the DLL on Windows 7 (I'd prefer not to), and will that cause the DLL to become unusable on the Windows XP machine?
Problem solved. The problem was that the Windows 7 machine did not have the KB971090 update which was installed on the Windows XP machine which built the DLLs. I had to explicitly tell Windows Update that I wanted to receive non-Windows updates in order to be able to install the update.
I have a machine with Vsiual Studio 2005 and Visual Studio 2008 and Windows SDK version 6.1 (Windows Vista). I am planning to install the latest SDK (Windows 7 and .Net 3.5 Service Pack1), but the MSDN Comptabilty document (http://msdn.microsoft.com/en-us/windows/dd146047.aspx) indicates that the latest SDK is not recommended with VS 2005.
I would like to check if the two SDKs can coexist on the same machine or the latest SDK will oevrride the older version and could cause issues with VS 2005.
Thanks
Just a word of warning, the 7.0 SDK has a badly broken installer. It hacks registry keys that are used by Visual Studio to find SDK components and drops files in the VS install directory. This can render it unusable. The worst problems are documented as sticky posts in the Windows SDK forum at the MSDN forums.
I had problems as well, the installer failed half-way through on my machine with a completely undescriptive error. On a pretty virgin machine with VS2008. It didn't roll back the install even though it failed, I had to edit the registry by hand to fix the damage.
I recommend you actually install the SDK on a machine you don't care about. Then copy the directory to a production machine and edit the VC++ directories yourself. Do strongly favor the v7.1 version instead. Good luck with it.
Should be fine as long as you don't try and install both versions of Visual Studio in the same folder. The SDK is essentially passive, you can have as many of them as you want installed, but you need to make sure that the paths that VS 2005 uses are to the older SDK rather than the newer one.
Since by default, the SDK is installed in a subfolder of the Visual Studio install folder, a long as you put different versions of VS in different folders, everything should work out fine all by itself.
Yes they can. I have 6.1 and 7.0 on one machine (Windows 7 64 bit no VS 2005 though) without any noticeable issues.
Definitely you can . u can set the sdk version u want to use each time .
This links tells how to set up your sdk versions in different visual studio versions.
http://msdn.microsoft.com/en-us/library/ff660764.aspx