Application Configuration Error C++ VS2005

[Tom]

I have built a VS 2005 C++ application (ported from VC++ 2003).
It's a WinForm app. It runs OK on the development system,
but when I try to deploy it on any other system, all users gets
an error box, "Applicatio n configuration Error. Try re-installing the
application. (Deployed using an MSI setup project).

I downloaded Dependency Walker, and it says that 2 DLL's
are not found:

DWMAPI.DLL, EFSADU.DLL

on the development machine. Well, it's true, they're not on the
development machine. I tried installing the BETA SP1 for
VS2005 standard edition - made no difference. I built in both
DEBUG and RELEASE configuations, no difference.

What the heck are the DLL's and how to fix the problem?

-- Tom

[Bruno van Dooren [MVP VC++]]

I have built a VS 2005 C++ application (ported from VC++ 2003).

It's a WinForm app. It runs OK on the development system,
but when I try to deploy it on any other system, all users gets
an error box, "Applicatio n configuration Error. Try re-installing the
application. (Deployed using an MSI setup project).

I downloaded Dependency Walker, and it says that 2 DLL's
are not found:

DWMAPI.DLL, EFSADU.DLL

on the development machine. Well, it's true, they're not on the
development machine. I tried installing the BETA SP1 for
VS2005 standard edition - made no difference. I built in both
DEBUG and RELEASE configuations, no difference.

What the heck are the DLL's and how to fix the problem?

Hi,

<from google>
DWMAPI.DLL is "Desktop Windows Manager" - the part of Windows Vista.

Do you perhaps have installed the VS plugins for writing .NET 3.0 apps?
I have also seen reports of this being caused by an IE7 (beta?) install.

Btw, that other computer does have the .NET2.0 framework installed, does it?

--
Kind regards,
Bruno.
br************* *********@hotma il.com
Remove only "_nos_pam"

[Tom]

OK, getting closer. Porting a setup project from 2003 to 2005
does not get all the dependencies to come along. I had to delete
and then add back some files to get the dependency checker to
work.

It then added a dependency:
policy_8_0_Micr osoft_VC80_CRT_ x86.msm

So it wants me to add a merge module to include the VC8.0 runtime.

Question: there are two merge modules:

policy_8_0_Micr osoft_VC80_CRT_ x86.msm

and

Microsoft_VC80_ CRT_x86.msm
Which one is the right one to include in the setup project?
-- Tom



"Bruno van Dooren [MVP VC++]" <br************ **********@hotm ail.comwrote
in message news:00******** *************** ***********@mic rosoft.com...

>I have built a VS 2005 C++ application (ported from VC++ 2003).
It's a WinForm app. It runs OK on the development system,
but when I try to deploy it on any other system, all users gets
an error box, "Applicatio n configuration Error. Try re-installing the
application. (Deployed using an MSI setup project).

I downloaded Dependency Walker, and it says that 2 DLL's
are not found:

DWMAPI.DLL, EFSADU.DLL

on the development machine. Well, it's true, they're not on the
development machine. I tried installing the BETA SP1 for
VS2005 standard edition - made no difference. I built in both
DEBUG and RELEASE configuations, no difference.

What the heck are the DLL's and how to fix the problem?

Hi,

<from google>
DWMAPI.DLL is "Desktop Windows Manager" - the part of Windows Vista.

Do you perhaps have installed the VS plugins for writing .NET 3.0 apps?
I have also seen reports of this being caused by an IE7 (beta?) install.

Btw, that other computer does have the .NET2.0 framework installed, does
it?

--
Kind regards,
Bruno.
br************* *********@hotma il.com
Remove only "_nos_pam"

[Bruno van Dooren [MVP VC++]]

Question: there are two merge modules:

>
policy_8_0_Micr osoft_VC80_CRT_ x86.msm

and

Microsoft_VC80_ CRT_x86.msm
Which one is the right one to include in the setup project?

I have not yet created installers with VS2005, but from what I can see:
both.
See here
http://blogs.msdn.com/aymans/archive...04/568466.aspx

--

Kind regards,
Bruno van Dooren
br************* *********@hotma il.com
Remove only "_nos_pam"

[t]

Thanks. The BLOG doesn't really go into the problem too clearly.
I deployed with just the one merge module: Microsoft_VC80_ CRT_x86.msm
even though SETUP listed the dependency as:
policy_8_0_Micr osoft_VC80_CRT_ x86.msm

I noticed a couple of things:

1) porting a SETUP project from VS2003 to VS2005 does NOT correctly
establish
the dependencies. I had to manually delete then re-add each exe file to the
SETUP project;
that correctly re-established the dependencies
(policy_8_0_Mic rosoft_VC80_CRT _x86.msm
in my case).

2) Deploying with the Microsoft_VC80_ CRT_x86.msm merge module alone was
sufficient
to get the application to work properly, there was no need to add the other
merge module.

3) Searching the web produces a lot of wrong information and incorrect
approaches
to the problem.

-- Tom


"Bruno van Dooren [MVP VC++]" <br************ **********@hotm ail.comwrote
in message news:uR******** *****@TK2MSFTNG P04.phx.gbl...

>Question: there are two merge modules:

policy_8_0_Mic rosoft_VC80_CRT _x86.msm

and

Microsoft_VC80 _CRT_x86.msm
Which one is the right one to include in the setup project?

I have not yet created installers with VS2005, but from what I can see:
both.
See here
http://blogs.msdn.com/aymans/archive...04/568466.aspx

--

Kind regards,
Bruno van Dooren
br************* *********@hotma il.com
Remove only "_nos_pam"

[Bruno van Dooren [MVP VC++]]

1) porting a SETUP project from VS2003 to VS2005 does NOT correctly

establish
the dependencies. I had to manually delete then re-add each exe file to
the SETUP project;
that correctly re-established the dependencies
(policy_8_0_Mic rosoft_VC80_CRT _x86.msm
in my case).

Good to know.

2) Deploying with the Microsoft_VC80_ CRT_x86.msm merge module alone was
sufficient
to get the application to work properly, there was no need to add the
other merge module.

That will depend on what your app uses. If you only use the CRT, then that
will suffice.

3) Searching the web produces a lot of wrong information and incorrect
approaches
to the problem.

Sad but true.
But I am glad your problem was solved.

--

Kind regards,
Bruno van Dooren
br************* *********@hotma il.com
Remove only "_nos_pam"

[t]

Thanks for the answers.

Under what case(s) would it be also necessary to deploy the policy_VC80_CRT
merge module? Do you know if there is any documentation available about
this?

-- Tom

>

>2) Deploying with the Microsoft_VC80_ CRT_x86.msm merge module alone was
sufficient
to get the application to work properly, there was no need to add the
other merge module.

That will depend on what your app uses. If you only use the CRT, then that
will suffice.

[Bruno van Dooren [MVP VC++]]

Under what case(s) would it be also necessary to deploy the

policy_VC80_CRT
merge module? Do you know if there is any documentation available about
this?

The main resource I use is MSDN, which has a section on redistributing
applications in the VC++ section.
Apart from that I use google when needed.
But I don't know any specific set of documentation which is complete.

--

Kind regards,
Bruno van Dooren
br************* *********@hotma il.com
Remove only "_nos_pam"