“The Microsoft Windows Software Development Kit Update for Windows Vista provides documentation, samples, header files, libraries, and tools you need to develop applications that run on Windows. This release of the SDK supplies updated compilers and documentation. The updated compilers are the same ones that recently shipped in Visual Studio 2005 Service Pack 1. This SDK also includes the samples, tools, headers, and libraries that shipped in the Windows SDK for Vista in November, 2006.”
Windows Software Development Kit Update for Windows Vista
21 Comments
-
2007-03-25 9:32 pmsegedunum
Secondly, Java is the most used language on the planet right now, and you need to either have or distribute the runtimes for it, as it works in exactly the same way as .net (or python, or perl, or any other managed language)
It’s fantastic that Microsoft wants to repeat the many mistakes there and amplify them further, isn’t it?
while linux wont guarentee a stable ABI accross MINOR revisions.
Firstly, we’re not talking about Linux. Secondly, go away and find out how Linux kernel development actually works. It has not been, and has never been, designed for people to attach binary blobs to – for various fundamentaly good reason.
-
2007-03-26 12:12 amgoogle_ninja
It’s fantastic that Microsoft wants to repeat the many mistakes there and amplify them further, isn’t it?
How is microsoft “amplyfing” the “mistake” of managed code?
Firstly, we’re not talking about Linux. Secondly, go away and find out how Linux kernel development actually works. It has not been, and has never been, designed for people to attach binary blobs to – for various fundamentaly good reason.
Granted, but that doesnt change the fact that microsoft is the most developer friendly platform currently in existance. This is the first real break in 10 years, Apple cant say that, and linux cant even remotely come close.
-
2007-03-26 10:05 amTBPrince
Granted, but that doesnt change the fact that microsoft is the most developer friendly platform currently in existance. This is the first real break in 10 years, Apple cant say that, and linux cant even remotely come close.
Correct. And that’s why people developed (and still do) for Windows and they don’t for Linux / Mac OS, which explains why those systems have a tiny market share on desktops.
I wonder if people actually understands why Microsoft spends billions in backward compatibility if it is so unnecessary… Maybe they like wasting their money…
Plus, I would say that Vista introduces partially-breaking changes, meaning that if you run your software as administrator (of course, if you REALLY REALLY need that old software), chances are you can run most of your old 9x software.
“People are expected to program with this, and not only that, but deliver a couple of shotgun barrels’ full of explosive dependencies as well.”
Say huh wha? What are these dependencies you speak of (no seriously, list them)? If you are targeting Vista, everything you need to run your code will already be on the target machine.
Most of the SDK is documentation. Almost all the rest of it is header files. A very small portion of it is either compilers, or WinFX runtime binaries. None of this stuff needs to be deployed.
Repeat after me…none of the SDK needs to be deployed with your applications. Say it twice before bed and call me in the morning.
-
2007-03-25 9:27 pmsegedunum
Say huh wha?
You don’t know any software vendors then?
If you are targeting Vista, everything you need to run your code will already be on the target machine.
Highlighting says it all. If experience with .Net is anything to go by, we will then have .Net 3.1, and not too far away, .Net 4.0 as well as some new dependencies to go with it, a Windows.Forms replacement – already. Maybe even Sharepoint. Deployment is a huge issue in the Windows world now, and MSDN development is an alphabet soup of dependencies and lovely ways you can use a machine gun to shoot yourself in the foot.
Microsoft just doesn’t understand this isn’t the 1990s anymore.
Repeat after me…none of the SDK needs to be deployed with your applications. Say it twice before bed and call me in the morning.
Read the above and come back when you know what it actually means. You simply haven’t, or don’t want to.
Edited 2007-03-25 21:33
“Win32 API has been same for last 8-10 years unlike anything in Linux. “
I may disagree. Things like the standard C library, the basic kernel functions and the tools of the base system are the same, they existed even before any “Windows”, and even before Linux. But I see your point. Linux is developing strongly in the last years. Allthough backwards compatibility is neccessary, it is not the only goal. New technologies require new subsystems or libraries with new APIs.
Entering the google query (( user32.lib “WINDOWS SDK” )) verifies my dim memories of the issues involved.
You need the headers to be sure of type-matching of course. But directly linking to the new user32.lib IIRC will either not work with Visual Studio 6, or it won’t load in XP due to unresolved externals, anyway I ended up calling the trusty GetProcAddress() for the new stuff and actually linking to an ancient version of user32.lib so as to not need GetProcAddress() for Everything.
SO if you want to conditionally use new stuff *IF* you’re running under Vista, be prepared for possibly a few hours of figuring this stuff out.
-
2007-03-25 10:45 am
-
2007-03-25 4:49 pmpg--az
My best machine is an ancient 2400-mhz Pentium 4, only one core, no hyperThreading.
Presumably you have multicore Xeon, that you can tolerate Visual Studio’s slowdowns. Try the Google query (( VISUAL STUDIO 2005 intellisense slow )).
Probably someone from the powertoys group must be responsible for the idea of updating the intellisense-database in-real-time as you edit the source – yes, fine for toy-size projects !
Thanks in advance if indeed you have a set of settings-tweaks that will acceptably speed it up.
That query did reveal at least one speedup-fix in SP1, which I have not installed yet – does that speed it up much ?
Nice to have most if not all of it in one downloadable package. If it’s an update purely for Vista support, it’s kinda late though.
Purely for Vista is correct. I cannot use it on this Linux system, therefore I cannot use this system to develop for Vista.
Does it let you install it under XP ?
Or do you need to have Vista running before you can use it ?
The time has come for Microsoft to open up a little more and let others using other systems develop for them…. if they feel they want to.
Ballmer himself was crying out for developers, why block them out now when you need them the most ?
I haven’t downloaded it yet, but if it’s just adding support for Vista I’d have to assume it’s installable on XP, otherwise they’d have to have a dedicated Vista package.
// The time has come for Microsoft to open up a little more and let others using other systems develop for them…. if they feel they want to. //
Agreed, however do you really want Microsoft to be developing for say a Linux environment? They’d likely want to control it in some way. I think the current method with the Mono project is best. It may lag a bit behind as new language is added / compilers are changed, but at least it’s open.
// Ballmer himself was crying out for developers, why block them out now when you need them the most ? //
Yeah I can see your point, though I’d have my doubts about OSS developers developing for a proprietary system like Windows… in mass anyway.
If you’re developing for Windows, you want to test for Windows. The Microsoft Toolchain does not pretend to develop software for a non-windows system and there is no need for a cross-compiler since Windows is a perfectly capable self-hosting environment. If you want to develop for Windows on Linux, why not try something that purports to be cross-platform, like GTK+, WxWidgets, or Qt? I think you’re complaining about nothing.
If you read the webpage then you will find out that it supports XP. It supports both installing on XP and developing for XP.
If you read the webpage then you will find out that it supports XP. It supports both installing on XP and developing for XP.
I can program for XP today without downloading and installing a gig’s worth of software updates and components, which I will then need to deliver with my applications to get them to do……..exactly the same things as they were doing before. It’s a waste of time.
It may be a waste of time for you but not for others. The good thing about the new SDK is that i can compile my existing programs with it and also explore the new APIs and use the power of new API in my software.
If you want to stay pedantic, then be that. But don’t try to come off as negative to something which is useful to others.
It seems you just hate Microsoft and that is why you are saying bad about the new stuff.
Given that your anti-Microsoft history, you are not trustworthy. Negative stuff like this is expected from people like you who are so biased.
Edited 2007-03-25 04:49
What a moving target that whole mess is.
Care to explain?
Win32 API has been same for last 8-10 years unlike anything in Linux.
Edited 2007-03-25 00:58
Care to explain?
Click the link above and have a look at the overview, and then put your software vendor’s hat on – if you have one. Fancy delivering applications like that to your customers?
Win32 API has been same for last 8-10 years
What’s the Win32 API got to do with anything? Have a look at the components in there (and this is about five minutes after Vista’s release). People are expected to program with this, and not only that, but deliver a couple of shotgun barrels’ full of explosive dependencies as well.
It seems as though the MSDN lunatics indeed have taken over. I suggest you read this:
http://www.joelonsoftware.com/printerFriendly/articles/APIWar.html
Click the link above and have a look at the overview, and then put your software vendor’s hat on – if you have one. Fancy delivering applications like that to your customers?
First of all, you don’t need to distribute .net 3.0 runtimes for vista, but you do need the .net 3.0 sdk if you want to program in it. Secondly, Java is the most used language on the planet right now, and you need to either have or distribute the runtimes for it, as it works in exactly the same way as .net (or python, or perl, or any other managed language)
What’s the Win32 API got to do with anything?
You comment on how much of a moving target developing for windows is when they change the api once a decade, while linux wont guarentee a stable ABI accross MINOR revisions.