About Web Services and C++ on Windows platform : VC++ Libraries Deployment

VS2005 SP1 does update VC++ redistributable MSMs in \common files\merge modules

NikolaD — Thu, 07 Jun 2007 03:34:00 GMT

I thought I should write a short post on this issue. It had been discussed before on forums and in bugs. Long story short, VS2005 SP1 does update all VC++ redistributable MSMs in \Program Files\Common Files\Merge Modules. Or I guess I should say, it is...(read more)

VS2005 SP1 version of Visual C++ Redistributable Package is available for download.

NikolaD — Tue, 24 Apr 2007 01:01:00 GMT

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: Visual C++ 2005 SP1 Redistributable Package (x64) Visual C++ 2005 SP1 Redistributable...(read more)

A solution to two references to different versions of CRT, MFC, ATL in one application manifest file

NikolaD — Thu, 29 Mar 2007 23:14:00 GMT

I have received several questions about a case when developers find two or more references to different versions of CRT or MFC or ALT libraries in application manifest. In this post I am describing root cause of the issue, the solution to the problem and possible workarounds....(read more)

Q&A on adapting VS2005 SP1 to build your applications

NikolaD — Sat, 10 Feb 2007 05:17:00 GMT

When VS2005 SP1 has been released, because of manifests it become more visible what version of VC++ DLLs are used at runtime by applications built with SP1. Devs have noticed that once they have built their application with VS2005 SP1, it wants to load...(read more)

Silent installs of VCRedist.EXE shipped with VS2005

NikolaD — Thu, 08 Feb 2007 21:34:00 GMT

Aaron has a post on his blog that describes way of silent install of VCRedist.EXE. I though I would cross-link it from my blog in case some folks are interested in this information. Here is the link http://blogs.msdn.com/astebner/archive/2007/02/07/update-regarding-silent-install-of-the-vc-8-0-runtime-vcredist-packages.aspx...(read more)

Junfeng Zhang describing ways of diagnosing SxS failures

NikolaD — Tue, 29 Aug 2006 02:03:00 GMT

Junfeng has an interesting walkthrough on how diagnose SxS failures and brief introduction of new tool available on Vista. One may find it here, http://blogs.msdn.com/junfeng/archive/2006/04/14/576314.aspx. ...(read more)

Norton WinDoctor errors about msvcr80.dll

NikolaD — Thu, 29 Jun 2006 03:29:00 GMT

Norton WinDoctor issuing errors about msvcr80.dll missing for files in .Net Framework 2.0 (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\) or Visual Studio 2005. These errors can safely be ignored. Please do not copy msvcr80.dll or any other dlls to System32 or C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ folders...(read more)

Applocal deployment of MFC localized resource DLLs

NikolaD — Tue, 25 Apr 2006 03:28:00 GMT

It was pointed out to me that it is not clear from Docs how to redistribute MFC localized DLLs with MFC application in application local folder. This post contains short example of application local deployment of MFC localized resource DLLs. ...(read more)

Visual C++ 2005 Redistributable Package is released to the web

NikolaD — Tue, 11 Apr 2006 19:55:00 GMT

VCRedist.exe can now be downloaded from the Microsoft site. This package contains VS2005 RTM versions of all VC libraries – OpenMP, MFC, ATL, CRT, MSDIA. You may use this exe to to make an application built with VC++ Express run on a computer that does not have VC++ 2005 Express installed. ...(read more)

Embed manifest with makefiles in VS2005

NikolaD — Thu, 23 Mar 2006 22:04:00 GMT

It is pointed out to me that MSDN example on how to embed manifest is focused on changes into one makefile. In this post I outline how one can change many existing makefiles to embed manifest....(read more)

VS2005 docs are online!

NikolaD — Wed, 19 Oct 2005 21:10:00 GMT

I would like to let readers know that most of material that I have on my blog in regard of Fusion and VC++ libs, manifests and other side-by-side things, all or most of this is already available in a form of VC++ docs online on http://msdn2.microsoft.com. It is actually online for quite some time, but it looks like folks still do not know about this site. Let me give you some overview of topics:

Deployment section (http://msdn2.microsoft.com/en-us/library/zebw5zk9(en-US,VS.80).aspx)
- Deeply hidden before, this section was brought up to the top level and contains answers to questions on how to deploy VC++ applications to another computer. It goes over practices, different deployment model (http://msdn2.microsoft.com/en-us/library/ms235316(en-US,VS.80).aspx) and examples (http://msdn2.microsoft.com/en-us/library/ms235285)
Building SxS C++ Apps and assemblies (http://msdn2.microsoft.com/en-us/library/ms235532(en-US,VS.80).aspx)
- Contains general information on manifest in C++ apps and dlls. Also high level description of how manifest is generated by VC++ IDE.

I would like to specifically mention two topics that should answer two most frequent questions:

how to embedded manifest inside a binary using makefiles (http://msdn2.microsoft.com/en-us/library/ms235591(en-US,VS.80).aspx)
troubleshooting (http://msdn2.microsoft.com/en-us/library/ms235342(en-US,VS.80).aspx).

Hope this may help you find information you are looking for. Also I would like to mention that Martyn has moved his blog to a new location (http://blogs.msdn.com/martynl/). One of his recent posts describes in details why VC++ had to change deployment model for VC++ DLLs, http://blogs.msdn.com/martynl/archive/2005/10/13/480880.aspx. Take a look and feel free to ask any questions.

Running C++ application built by VC++ Express on another computer

NikolaD — Sat, 03 Sep 2005 05:15:00 GMT

Another FAQ from VC++ Express users is: "I give my VC++ application to my friend, and it does not run on her computer." This happens because VC++ Dlls have to be redistributed to another computer together with this application.

There are three ways to get an application built with VC++ Express 2005 to run on another computer that does not have VC++ Express installed:

Ask user of that computer to install Visual C++ Redistributable Package (VCRedist_x86.exe) to install all Visual C++ libraries as shared side-by-side assemblies into the native assembly cache (WinSxS folder). This package can be downloaded from the Microsoft download site Microsoft Visual C++ 2005 Redistributable Package (x86). Redistributing Visual C++ libraries using this package is recommended for applications built with Visual C++ Express.
Build another installer of VC++ libraries using Redistributable Merge Modules installed by VC++ Express into Common Files\Merge Modules. I am describing this approach below in more details.
Statically link your application to VC++ libraries. I recommend against statically linking because static linking prevents your application from running against the most up todate version of VC++ libraries installed on your computer. For example, consider an application that is statically linked to a particular library, running on a client computer with a new version of this library. The application still uses code from the previous version of this library, and does not benefit from library improvements, such as security enhancements.

So if you have decided that you cannot use Microsoft Visual C++ 2005 Redistributable Package (x86) and wisely avoid statically linking to VC++ libraries, you may build a custom MSI that deployes VC++ libraries using four merge modules with CRT library installed by VC++ Express. In my case there are installed in D:\Program Files\Common Files\Merge Modules\:

D:\Program Files\Common Files\Merge Modules\

microsoft_vc80_crt_x86.msm

policy_8_0_microsoft_vc80_crt_x86.msm

microsoft_vc80_debugcrt_x86.msm

policy_8_0_microsoft_vc80_debugcrt_x86.msm

Clearly I assume that you have read the EULA and redist.txt and do understand that redistribution of debug applications is not allowed. You can simulate redist of debug binaries in your office, but if it goes outside to another computer, it must be application build in Release mode. So please read the EULA and redist.txt carefully and understand what you can and what you cannot redistribute.

I am going to show now how to one can use MSMs to install VC++ DLLs to another computer. I have VC++ Express installed on my computer and I want to make it run on another computer that does not have VC++2005 installed. Here is what I do:

1. I download WIX from sourceforge.net, here is the link http://sourceforge.net/projects/wix . More specific I am going to download from this link, http://prdownloads.sourceforge.net/wix/binaries-2.0.3220.0.zip?download but you may use another build of WiX, perhaps more recent or older then one I use.

2. I am going to unzip this package to D:\WiX\

3.Now I am going to open Visual Studio 2005 Command Prompt (Start>All Programs>Visual C++ 2005 Express Edition>Visual Studio Tools>Visual Studio 2005 Command Prompt)

4. I am typing uuidgen –n2 and click Enter. This generates two UUIDs for me that I am going to use later in Step 6.

5. Now I am going to create two XML files in D:\WiX. First VCCRT.wxi, second VCCRT.wxs.

6. First, I am creating D:\WIX\VCCRT.wxi with the following content :

<?define PRODUCT_ID=!!!! REPLACE WITH UUID1 FROM STEP 4 !!!! ?>

<?define PACKAGE_ID=!!!! REPLACE WITH UUID2 FROM STEP 4 !!!! ?>

</Include>

Attn: I am going to use two UUIDs generated for me by uuiedgen.exe in the Step 4 to define PRODUCT_ID and PACKAGE_ID. On purpose, I am not listing UUID generated for me, so to help readers of this article avoid using same UUID as someone else.

7. Second, I am creating D:\WIX\VCCRT.wxs with following content

<?xml version='1.0'?>

<?include $(sys.SOURCEFILEDIR)\VCCRT.wxi ?>

<Product Id='$(var.PRODUCT_ID)'

Name='MSI to redistribute my app'

Language='1033' Version='1.0.0.0' Manufacturer='Me'>

<Package Id='$(var.PACKAGE_ID)'

Description='MSI to redistribute my app'

Comments='MSI to redistribute my app'

Manufacturer='Me'

InstallerVersion='300'

Compressed='yes' />

</Directory>

</Feature>

</InstallExecuteSequence>

</Product>

</Wix>

8. Now I am going back to command line, change current directory, compile and link msi

>cd d:\WiX
>candle.exe vccrt.wxs -out vccrt.wixobj
>light.exe vccrt.wixobj -out vccrt.msi

9. That's it, MSI is created. It should be a file D:\WiX\vccrt.msi. If you see errors, take a look on troubleshooting section below.

10. Now I copy my application and vccrt.msi to another computer where I want this application to run which does not have VC++ Express installed. After I have copied my EXE and vccrt.msi, I will first run vccrt.msi before running my EXE.

11. Well my application works just fine. If your application does not start after MSI is installed, please see TroubleShoting section below.

Troubleshooting:

1. Error message CNDL0054 from candle.exe

candle.exe : error CNDL0054 : The document element name 'Include' is invalid. A WiX source file must use 'Wix' as the document element name.

Cause: you have tried executing >candle.exe vccrt.wxi -out vccrt.wixobj instead of >candle.exe vccrt.wxs -out vccrt.wixobj

2. Error message CNDL0009 from candle.exe

D:\WiX\vccrt.wxs(6) : error CNDL0009 : The Product/@Id attribute's value, '!!!! REPLACE WITH UUID FROM STEP 4 !!!! ', is not a legal guid value.

D:\WiX\vccrt.wxs(10) : error CNDL0009 : The Package/@Id attribute's value, '!!!! REPLACE WITH UUID FROM STEP 4 !!!!', is not a legal guid value.

Cause: Edit vccrt.wxi and replace !!!! REPLACE WITH UUID FROM STEP 4 !!!! with UUID generated in Step 4

3. Error Message CNDLXXXX from candle.exe

Cause: No idea, mistake happen when you copy/pasted XML from this post. See WiX documentation for troubleshooting.

4. Error on start of application either a message box that says "This application has failed to start because the application configuration is incorrect" or "The system cannot execute the specified program"

Cause: First, check that your application is built in Release mode. If it was Debug application, you will see OS errors that let you know that either msvcm80d.dll or msvcr80d.dll is not loaded. Second, check if you have deployed all Dependencies of this application. Use depends.exe to see dependencies of an application

5. Error message box while starting your application that says "To run this application you first must install .Net Framework of version v.2.0.xxxx".

Cause: You application contains managed code and depends on presence of .Net Framework. For C++ applications it means that it has been compiled as /clr, /clr:pure or /clr:safe. You have install .Net Framework.

6. After you have installed MSI and you run your application you still get errors described on this page in MSDN , please make sure you have done all steps exactly as they are described and repeat them. Also check out general troubleshooting section in MSDN docs for issues around deployment of Visual C++ libraries.

For any additional help with redistributing applications built with VC++ Express, please check out discussions or ask your question on VC++ Forums, http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=29&SiteID=1.

Fusion Docs

NikolaD — Thu, 09 Jun 2005 07:58:00 GMT

I am helping our UE team (folks that work on MSDN docs) with topics on Fusion and how to debug Fusion errors. I have finished today another section on how to deal with well-known and sincerely loved error dialog "The System cannot execute the specified program". Please send me any feedback on this topic, except grammar and spelling errors :-). I have built it using setup anyone can find in Beta 2, so it should be easy to follow. Here is the link

Why I see ''Embedding manifest...'' message in Output window?

NikolaD — Sun, 05 Jun 2005 11:09:00 GMT

Well, time flies fast. It was two month since my last post here. One may ask what I was doing all this time. Answer is simple – working. :-) Seriously, VC++ program management team has spent a lot of time in preparing and then running VC++ Tour in Europe. There is long slides deck with information on all features coming in VC++ 2005 and several demos for most frequently asked features. Take a look on official page for this trip for more information http://msdn.microsoft.com/visualc/community/Tour2005/ . Also during our stop in Norway, my laptop was ambushed by Pepsi. It was seriously damaged and for the rest of the trip I was only able to check my emails from internet cafes. However very soon I started to have issues with remote connectivity, and that was the end of e-life for me. Anyway, it is the second week I am back in my office and hopefully I will post more regularly now.

So if you use VS2005 Beta 2 (yes, yes, it is available now, go ahead and download it if you have not done this already), you may have already noticed a message saying “Embedding manifest…” when you are building you project. You may also notice that linking starts second time sometimes after this message. You may ask yourself, what is going on and why we link twice. Actually 2^nd link starts only if incremental linking or edit-and-continue is enabled. By default Visual Studio tryes embedding manifest for each project, unless users explicitly changes Manifest Tool -> Input and Output -> Embed Manifest property in Project Properties dialog. If the user selects to not embed manifest, manifest is generated as an external file and saved in the same directory where the final binary is. If the user chooses to embed the manifest, IDE embeds final manifests using the following process:

1. After the user code is compiled to object files, the linker collects dependent assembly information and while linking the final binary it generates an intermediate manifest that is used later to generate the final manifest.

2. After the intermediate manifest and linking are finished, the manifest tool will be executed to merge a final manifest.

3. If neither incremental linking nor edit-and-continue are enabled, mt.exe embeds the final manifest into the binary. If incremental linking or edit-and-continue is enabled, mt.exe save it as an external file. And project system is going to start second incremental linking to embed this external file.

4. Project build system then detects whether the manifest generated by the manifest tool contains different information then the manifest already embedded in the binary.

5. If the manifest embedded in the binary is different from the manifest generated by the manifest tool or binary does not contain an embedded manifest, IDE will invoke the linker one more time to embed the external manifest file inside the binary as a resource.

6. If the manifest embedded in the binary is the same as the manifest generated by the manifest tool, the build will continue to the next build steps.

So why does IDE need steps 4-6? The issue here is that in order for incremental linking to work, no changes should be made to the binary after it was linked by the linker. If mt.exe embeds manifest after the linker, the on the next incremental link, the linker detects the change and spins the full build. But if IDE creates a resource file with the final manifest and ask the linker to link this resource with the already built binary, for the linker this is a simple and very quick job to do. Moreover after resource is embedded, the binary is still correctly formed for the next incremental link. Nice trick by IDE, isn’t it?

Manifest is embedded inside the final binary as a text resource and it can be viewed by opening the final binary as a file in Visual Studio. Just open this binary in IDE and you see binary resource. Export it and you can now view it with any text editor. Actually this is the first step when I need to debug why this binary does not load.

So the fair question is what someone does to existing makefiles? Well, I have posted a sample where I have shown how to change a makefiles used to build both EXE and DLL. You may find it here How to embed manifest inside C/C++ program using makefiles.

Questions? Please feel free to post any comments below, I will try replying asap.

Resolving your dependencies on VC++ libraries in VS2005 Beta 1

NikolaD — Fri, 18 Mar 2005 20:46:00 GMT

This article does not apply to final release of VS2005. Steps outlined below were only required in VS2005 Beta2. For an example that demonstrates recommended steps in final release of VS2005 please see http://msdn2.microsoft.com/en-us/library/ms235285.aspx

Another FAQ. As you may already know from VS2005 Beta 1 or CTPs, Visual C++ 2005 supports a new deployment model for Windows-client applications using isolated applications and side-by-side assemblies. The ATL, MFC, and CRT libraries are now side-by-side assemblies that are installed in WinSxS folder and can be shared at runtime by isolated applications. Building your C/C++ program as an isolated application and developing your assemblies as shared side-by-side assemblies has number of advantages. Such isolated applications are not unaffected by changes to the registry, other applications installing same DLLs or other versions of assemblies running on the system. The sharing of side-by-side assemblies after deployment on either a global or per-application basis can be easily controlled by application's authors or system administrators. This also simplifies servicing of already deploy applications and provides a way to avoid DLL versioning conflicts caused by an incompatible versions of DLLs installed on the same client machine. If you are not familiar with isolated applications and side-by-side assemblies deployment model a good point to start is to read

About Isolated Applications and Side-by-side Assemblies

However, let's go back to questions I am often asked. How to redistribute VC++ libs in applocal? In Beta 1 and Beta 2 the answer is:

- Go to Windows\WinSxS and find assembly and Dlls you are interested in. For example, let's assume you are interested in the CRT and STL DLLs on x86. Then you are looking for directory x86_Microsoft.VC80.CRT_[staff]_8.0.50110.4359_[staff] with msvcr80.dll and msvcp80.dll. This 8.0.50110.4359 is the assembly version, remember it for future. Check that version of the compiler you are using matches to version of this assembly.

- Copy these two Dlls to your application local folder.

- Go to Windows\WinSxS\Manifests\ and find 636 x86_Microsoft.VC80.CRT_[staff]_8.0.50110.4359_[staff].manifest.

- Copy this manifest to application local folder.

- Rename this manifest to Microsoft.VC80.CRT.manifest. Basically name of the manifest has to match name of the assembly (it can be find on the 4th line of the manifest if you view it).

- Copy your app and Dlls and manifest to another computer where VS2005 is not installed. Try to run it and it should run.

We are considering make it simpler on RTM and have several solutions in mind. Will see what comes up from discussions.

Hope this works for you and makes world of IA and SbySA somewhat clearer.