Latest vcbuild.exe? - visual-studio

What software package provides the latest version of vcbuild.exe?
As far as I know, this tool is distributed with certain older versions of Microsoft's Windows SDK and Visual Studio. On my system, there is v7.1 of the SDK, and vcbuild.exe is not included, at least not in the default install.

To the best of my knowledge, vcbuild is not supplied with the Windows SDK. It is supplied with Visual Studio.
According to this MSDN blog article, vcbuild was retired after VS2008. It is included in VS2008, but not VS2010.

Related

Visual Studio WDK integration Issue

Recently I installed Visual Studio 2017 Enterprise along with WDK 10 for 1709 My workloads contained C++ workload. . My machine is a Windows 8.1 Pro with net framework 4.6.1. After installing the WDK I expected the templates to come in the Legacy section of Visual C++ but no legacy option is present in it. I don't understand what is the problem. Please help me.
Thanks in advance
I resolved the issue. It was due to a missing windows 10 SDK. Reinstallating the WDK with appropriate SDK solved the problem
Developing drivers to windows is quite interesting one will be exposed to advanced Operating System Concepts. The set up for the environment will be IDE
IDE - Visual Studio (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16)
Compilers (WDK)
Debugger (WDK)
WDK contains both(https://go.microsoft.com/fwlink/?linkid=2085767). Latest Visual Studio(VS2019) will come along with the latest WDK(10, 1903 as of now).
Sometimes plugins might not work properly i.e integration issues between Visual Studio and WDk.
By going to the location "C:\Program Files (x86)\Windows Kits\10\Vsix\VS2019" and run VSIX installer.
Now in a new project, driver related templates are available.

In which version of Windows did each VC++ re-distributable become standard?

My understanding is that the VC++ redists are essentially updates to some core Windows files, and that over time MS "catches up" by incorporating past versions into new versions/updates to Windows. For instance I'd probably expect anything built with VC++ 2005 wouldn't need me to install the redist on target PCs these days.
Can anyone provide definitive reference for which versions of Windows include which VC++ redist versions?
Also, is the redist approach something MS still employ in the newest versions of VC++ e.g. 2012 and later?
None of the files distributed with modern versions of Visual Studio are updates to files that ship with Windows.
Windows does ship with a C runtime, which is used internally and (for reasons of backwards compatibility) by applications built with Visual Studio 6 or earlier versions. Later versions of Visual Studio each have their own runtime, none of which are shipped with Windows.

Build C++/C# created with Visual Studio 2012 without VS 2012 being installed?

If I have a Visual Studio Solution file of VS2012 with few C++ native projects and a few C# projects, can I build this solution without installing Visual Studio 2012 itself?
This would ease (among other things) the maintenance on our Build-Server nodes.
You will need to install VS2012 Express.
Based on Microsoft documentation:
The Windows SDK no longer ships with a complete command-line build environment. You must install a compiler and build environment separately. If you require a complete development environment that includes compilers and a build environment, you can download Visual Studio 2012 Express, which includes the appropriate components of the Windows SDK.
There's also SharpDevelop... That should be able to build whatever you need. You may need to install the SDK, too- not sure. But it's quite a bit more lightweight than VS (express or not). And there's always Mono (and MonoDevelop/Xamarin Studio) for the C# and LLVM, MinGW and LCC for the C/C++ compilation, should you feel Microsoft's compilers have cooties. LLVM just released their first version for Windows not long ago, but it seems pretty solid... MinGW has been working on Windows for ages (and cross-compiling to Windows from various POSIX OSes, to boot). LCC can be slightly flaky at times, but it's tiny. I think the licensing is a bit restrictive, too, but you'll want to check yourself if that's the route you intend to go.
Also... just found this: Walkthrough: Using MSBuild to Create a Visual C++ Project.

Using the Windows 7 and DirectX SDKs with VS2005

I have Visual Studio 2005 and want to teach myself DirectX in my free time. I downloaded the latest Windows 7 and DirectX SDKs. According to Microsoft's website, the latest DirectX SDK is not compatible with Visual Studio 2005 (I assume they mean it's not compatible with the SDK it came with). Can I configure VS2005 to use the SDKs I downloaded instead of the SDK it came with? If so, is there anything I should be particularly careful with?
The June 2010 DirectX SDK no longer supports Visual Studio 2005. You need to download an older version of the SDK and you'll be fine.
I'd wager you can encourage June 2010 to run under 2005. You may need to modify your headers slightly to make them 2005 compatible but the DX DLLs don't care what they get dynamically linked to by ... Install the SDK set up the include and library paths to point at the DirectX sdk ... compile and see what errors you get.

Can two different Windows SDK versions coexist on the same machine without conflict?

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

Resources