VS 2005, problems with manifest and unmanged code
- From: guenter.pesch@xxxxxxx
- Date: Wed, 24 Sep 2008 07:24:39 -0700 (PDT)
Hi,
we have a problem with manifests in our applications.
The applications are Windows applications, developed in Visual Studio
2005, with unmanaged C++/MFC. The MFC library is statically linked, so
we normally do not need any setup, because the .exe is enough.
The projects were formerly created with Visual Studio 2003 and then
converted to 2005.
With Visual Studio 2005, a manifest is automatically embedded. We are
a little bit worrying about this, because in our opinion a manifest
makes sense with mangaged .NET applications, but we have unmanaged C++/
MFC applications, but anyway.
Now we have two applications, let's say A and B. The start of A fails
with the message:
"The application has failed to start because the application
configuration is incorrect. Reinstalling the application may fix this
problem."
When I change the project setting to 'not embed manifest', A is
working fine.
Application B works fine with or without manifest.
We tried a lot to find out the reason for the different behavior of
our applications, but without any success.
The manifest files of A and B are identical, the project settings are
nearly the same and the depending modules the applications need are
the same (we checked with DependencyWalker),
Does anybody have an idea, why application B is working fine even with
an embedded manifest?
Thanks in advance.
.
- Follow-Ups:
- Re: VS 2005, problems with manifest and unmanged code
- From: David Wilkinson
- Re: VS 2005, problems with manifest and unmanged code
- From: Christoph Conrad
- Re: VS 2005, problems with manifest and unmanged code
- Prev by Date: Re: The term "Callback Function"
- Next by Date: Re: VS 2005, problems with manifest and unmanged code
- Previous by thread: Use a DC in a worker thread
- Next by thread: Re: VS 2005, problems with manifest and unmanged code
- Index(es):
Relevant Pages
|