Comments on: Howto: Deploy VC2008 apps without installing vcredist_x86.exe

By: Vs2008 compile the program can’t run out or need to install the vcredist_x86. Exe to run a solution

Tue, 26 Jul 2011 19:16:26 +0000

[…] Howto: Deploy VC2008 apps without installing vcredist_x86.exe […]

By: App-V FAQ #31: Can I virtualize the .NET Framework or Visual C++ Redistributables? | Aaron Parker

Tue, 14 Dec 2010 14:01:52 +0000

[…] Howto: Deploy VC2008 apps without installing vcredist_x86.exe […]

By: links for 2010-07-31

links for 2010-07-31 — Sat, 31 Jul 2010 22:02:41 +0000

[…] Howto: Deploy VC2008 apps without installing vcredist_x86.exe (tags: programming python windows) […]

By: jkalmbach

jkalmbach — Thu, 15 Jul 2010 16:56:49 +0000

Maybe you have forgott to remove the publicKeyToken? Or you have other DLLs which have a embedded manifest with the publicKeyToken?

By: Chronogps

Chronogps — Thu, 15 Jul 2010 16:32:00 +0000

I followed the tutorial but I get a 0xC0150002 error (missing DLL I supposed). Any idea ?

By: Sequence Ecowin Pro 6 | Application Distribution Blog

Sequence Ecowin Pro 6 | Application Distribution Blog — Mon, 12 Jul 2010 06:18:25 +0000

[…] reading among various articles that hopefully would give a hint – something came up. A guy named Jochen had described a solution to making SidebySide local (meaning placing them in the same folder as the […]

By: Jochen Kalmbach’s Blog » Blog Archive » Deployment of VC2008 apps without installing anything

Mon, 10 May 2010 09:00:59 +0000

[…] Just a small note: You should be aware, that this “AppLocal” installation is not really “AppLocal”… it is only AppLocal, if the vcredist_*.exe was not installed. If the vcredist_*.exe is installed, then the DLLs from the WinSxS directory will be used. If you want to prevent this, you can do a really AppLocal deployment. […]

By: jkalmbach

jkalmbach — Fri, 16 Apr 2010 16:24:48 +0000

You have some kind of “bug” in one of your dependencies… you must not deploy debug versions!

By: Bruno

Bruno — Fri, 16 Apr 2010 15:40:33 +0000

Hey, Sorry for this second message. I also noticed that my manifest file is looking for Microsoft.VC80.CRT & Microsoft.VC90.DebugCRT: I could find VC90.DebugCRT in (ProgramFiles\Microsoft Visual Studio 9.0\VC\redist\Debug_NonRedis\x86) the Visual Studio folder (VS 2008 Professional Edition) but I cannot find the VC80. Can anybody tell me what should I do??? Thanks, Bruno

By: jkalmbach

jkalmbach — Fri, 16 Apr 2010 15:23:08 +0000

If you want an external manifest, you need to disable the embedding of the manifest. See Manifest options (Project-Properties|Manifest Tool|Input and Output|Embed Manifest: No)

By: Bruno

Bruno — Fri, 16 Apr 2010 15:20:38 +0000

Hi everybody,

I am trying to solve this problem but I have a question. Where do I find the external manifest of my project? When I went to the Debug folder all I can find is app.exe.embed.manifest and app.exe.intermediate.manifest??? Or should I just create it myself???
Thanks,

Bruno

By: Svetoslav Kyuchukov

Svetoslav Kyuchukov — Fri, 21 Aug 2009 11:20:49 +0000

Hello Jochen,

Thanks for the useful article. The described technique work also fine for deploying of debug versions, by working with corresponding debug folders and manifest files:
(Microsoft.VC90.DebugCRT, Microsoft.VC90.DebugCRT.manifest, etc.)
Currently I work on a VS2008 solution that contain 4 executables and 18 dlls, and deploying debugs is a practical (for Testers, PMs, etc. purposes).

And further, even the Common Control Dll (comctl32.dll) can be deployed locally, skipping the WinSxS. This can be done with the following steps:

1. Create a folder “Microsoft.Windows.Common-Controls” in deployment exe folder, for example
MyApp\exe\Microsoft.Windows.Common-Controls

2. copy comctl32.dll file from C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a folder
into MyApp/exe/Microsoft.Windows.Common-Controls folder

3. copy x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.Manifest file from C:\WINDOWS\WinSxS\Manifests folder
into MyApp/exe/Microsoft.Windows.Common-Controls folder

4. rename x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.Manifest to Microsoft.Windows.Common-Controls.Manifest

5. remove publicKeyToken from this new manifest (Microsoft.Windows.Common-Controls.Manifest)

6. in all dlls and exes manifests remove publicKeyToken from the section described “Microsoft.Windows.Common-Controls”.

Now comctl32.dll is deployed locally, and WinSxS is bypassed.

Best regards,
Svetoslav Kyuchukov

Eurorisksystems Ltd.
Varna, BG

By: jkalmbach

jkalmbach — Wed, 27 May 2009 19:33:04 +0000

For appLocal deployment, without removing the publicKeyToken, see:

Deployment of VC2008 apps without installing anything
http://blog.kalmbach-software.de/2009/05/27/deployment-of-vc2008-apps-without-installing-anything/

By: jkalmbach

jkalmbach — Wed, 06 May 2009 16:22:15 +0000

Remove all config-files and just remove the publicKeyToken!!!!!!

By: IMMI

IMMI — Wed, 06 May 2009 14:33:49 +0000

Hi Jochen, Sorry! i have been trying to add code alongwith the tag symbols but unable to add. So, putting (tag) instead of each angle bracket… Hp u understand

Application.exe.manifest
——————————

(tag)assembly xmlns=”urn:schemas-microsoft-com:asm.v1″ manifestVersion=”1.0″(tag)
(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.ATL” version=”8.0.50727.762″ processorArchitecture=”x86″ (tag)(tag)/assemblyIdentity(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.CRT” version=”8.0.50727.762″ processorArchitecture=”x86″ (tag)(tag)/assemblyIdentity(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.MFC” version=”8.0.50727.762″ processorArchitecture=”x86″ (tag)(tag)/assemblyIdentity(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.MFCLOC” version=”8.0.50727.762″ processorArchitecture=”x86″ (tag)(tag)/assemblyIdentity(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)
(tag)/assembly(tag)

——————————————————————————

Application.exe.config
————————-

(tag)configuration(tag)
(tag)runtime(tag)
(tag)assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″(tag)
(tag)publisherPolicy apply=”no”/(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.ATL” version=”8.0.50727.762″ processorArchitecture=”x86″/(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)bindingRedirect oldVersion=”8.0.41204.256-8.0.50608.0″ newVersion=”8.0.50727.762″/(tag)
(tag)bindingRedirect oldVersion=”8.0.50727.42-8.0.50727.762″ newVersion=”8.0.50727.762″/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.CRT” version=”8.0.50727.762″ processorArchitecture=”x86″/(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)bindingRedirect oldVersion=”8.0.41204.256-8.0.50608.0″ newVersion=”8.0.50727.762″/(tag)
(tag)bindingRedirect oldVersion=”8.0.50727.42-8.0.50727.762″ newVersion=”8.0.50727.762″/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.MFC” version=”8.0.50727.762″ processorArchitecture=”x86″/(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)bindingRedirect oldVersion=”8.0.41204.256-8.0.50608.0″ newVersion=”8.0.50727.762″/(tag)
(tag)bindingRedirect oldVersion=”8.0.50727.42-8.0.50727.762″ newVersion=”8.0.50727.762″/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)dependency(tag)
(tag)dependentAssembly(tag)
(tag)assemblyIdentity type=”win32″ name=”Microsoft.VC80.MFCLOC” version=”8.0.50727.762″ processorArchitecture=”x86″/(tag)
(tag)publisherPolicy apply=”no”/(tag)
(tag)bindingRedirect oldVersion=”8.0.41204.256-8.0.50608.0″ newVersion=”8.0.50727.762″/(tag)
(tag)bindingRedirect oldVersion=”8.0.50727.42-8.0.50727.762″ newVersion=”8.0.50727.762″/(tag)
(tag)/dependentAssembly(tag)
(tag)/dependency(tag)

(tag)/assemblyBinding(tag)
(tag)/runtime(tag)
(tag)/configuration(tag)

————————————————————————————

By: IMMI

IMMI — Wed, 06 May 2009 14:27:34 +0000

assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"

By: IMMI

IMMI — Wed, 06 May 2009 14:22:07 +0000

/* Application.exe.manifest Application.exe.config */

By: IMMI

IMMI — Wed, 06 May 2009 14:19:26 +0000

Hi Jochen, Hp ur fine... Yeah i have tried it so but the problem is still there. Infact i have done some workaround with Application Manifest as well as Application Configuration Files but all in vain as application is still not running. I m sending you a snippet of Application Manifest file that i have done. It may help you guide me more precisely... Application.exe.manifest Application.exe.config Thnx in advance...

By: jkalmbach

jkalmbach — Wed, 06 May 2009 06:16:18 +0000

Nom you cannot enforce external manifests (only in XP, but not in Vista). Therefore you need to modify the embedded manifest. But this should work….
But if you are not the developer of this application, you should contact the developer!

By: IMMI

IMMI — Wed, 06 May 2009 06:14:05 +0000

Hi jKalmbach,

Hp ur Fine and thnx for showing interest.

OK! i have removed the publicKeyToken entry from all of my DLL-manifests. However, as i have stated earlier that the application i m working on is provided to me for release and i cannot do anything for development. It has its EXE-manifest embedded in it as there is no external manifest file found.

Also, I have used a manifest extractor software “Resource Tuner” through which i have found an embedded manifest listed referring to the assemblies (CRT, MFC, Common-Controls). I have tried to make an application manifest myself just like the embedded one but It didnot work.

Is there any way to enforce application to use an external manifest instead of an embedded manifest file? or Is there any role Application Configuration File?

Thanx in advance.