This blog is about developing Windows applications using Visual Studio. All postings on this weblog are provided "AS IS" with no warranties, and confer no rights. Use of any samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Your host Nikola Dudar is a Program Manager in Windows division of Microsoft Corporation. He has been working on Windows Web Services API during Windows 7 and various additions to Visual C++ during VS2005 and VS2008. More details are in LinkedIn profile under Nikola's formal name Mykola Dudar.
If you are interested in program management and project management, check out my other blog at http://www.pmsnack.com/ where I collect best practices and other topics interesting to program and project managers.
To send feedback, comments or requests for new posts, please use the contact form.
Actually it has been available for download for several days now, but I was looking on Orcas features and completely forgot to mention it on my blog. Here they are:
You can use the to install SP1 versions of VC++ libraries on computers that do not have Visual Studio installed. You need SP1 version of VC++ libraries for applications that you build with VC++ Express SP1 or Visual Studio 2005 SP1.
BTW it does not require Windows Installer 3.0, it works just fine with Windows Installer 2.0. And yes, it can be installed on Windows Vista. I guess they are re-using old templates I have been created for RTM release of VCRedist.EXE. I will have to check with VC Release folks on that.
A reader of the previous post on my blog has posted two questions about using SP1 version of VCRedist.EXE
People, it would be nice if in the future you'll do it same time with releasing of Service Pack.
Microsoft Visual C++ 2005 SP1 再頒布可能パッケージがリリースされたようです。
How do I determine by program which is the latest version of the MFC 8 installed ?
I'd like to emulate the installation of the Redistributable Package (x86)
to distribute an application on a machine without Visual Studio installed.
Indeed, we'd like to avoid intrusive softwares, which require administrator
privilege to be executed.
Previously, we simply have to copy the Redistributable dlls + manifest
in the local application directory and all was fine. But since the SP1 version,
this strategy does not work anymore. Looking around I found some posts that
suggerated to create an application config file in order to rebind any previous
version to the new version of the dlls (i.e. the SP1 Redistributable dlls
located in the local application folder).
Here is my executable config file (application.exe.config), which rebinds old versions to the new dlls (SP1) :
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0" newVersion="8.0.50727.762"/>
<bindingRedirect oldVersion="8.0.50727.42-8.0.50727.762" newVersion="8.0.50727.762"/>
Without the config file the application does not start, and with the config file
it starts but crashes... I drag the application to Dependency Walker and it shows
that the new dlls are correctly referenced by all modules.
I've tested the application on a machine with the package installed and it worked fine.
I looked to the WinSxS folder and found a similar rebinding in the policy files.
Maybe the Redistributable Package makes something more that allows the application
to run correctly (registry edition, ...) ?
Any help is welcome.
The Microsoft Visual Studio 8\VC\redist\x86\Microsoft.VC80.ATL.manifest Doesn't seem to have been updated to the latest version "8.0.50727.762".
But don't Worry it's updated in Orcas!