On Wed, 27 May 2009, Sisyphus wrote: > > I currently have the "Microsoft Platform SDK for Windows Server 2003 > R2" compiler. I would like to also install "Windows SDK for Windows > Server 2008 and .NET Framework 3.5" from > http://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en > > Will installation of the latter clobber the former in any way ? > It's important that I don't lose the 2003 version, as it seems to be no > longer readily available from MS. (All links to it quickly turn into links > to the 2008 version when it comes to strating a download.)
Really? I didn't have any problems finding and downloading it so far: http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en I normally don't use the web install as I have a complete download sitting on a local disk normally, but it looks like the web install is still working too. > But I *would* like to be able to switch between the two. Will that be > possible if I go ahead and install the 2008 version ? Yes, they install into different directories. The 2003 version is even still called the "Platform SDK" while the 2008 version is now called the "Windows SDK". You can install multiple SDKs on the same machine; just make sure you don't let it set up environment variables automatically but use the setenv.cmd for each version as you need it. > On an on-topic note .... does the unavailability of the 2003 version mean > that, at some stage, it will be no longer used to build the x64 versions of > ActivePerl ? That's a pretty vague question. It is entirely possible that "at some stage" we will switch the compiler used to build ActivePerl for x64, but being unable to download the 2003 SDK would not be enough of a reason. I believe (but have not tested this) that it should be possible to compile additional modules with the 2008 compiler and use them with the 2003 compiled ActivePerl. It may require a patch to ExtUtils::MM_Win32 in the already released versions of ActivePerl to handle the manifest binding correctly, but otherwise it should just work. The advantage of the 2003 SDK compiler for x64 (and VC6 for x86) is that they don't require additional runtime libraries; they link against MSVCRT.dll which is already part of Windows. So any application generated with PAR / PerlApp / Perl2Exe doesn't need to bundle MSVCR80.dll. Cheers, -Jan _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
