By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,602 Members | 1,473 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,602 IT Pros & Developers. It's quick & easy.

Manifest and config file together with unc path

P: n/a
Hi,
I have a managed app running from an unc path on the local intranet (Full
trust is set for this path with the .NET Configuration mmc!). If the
applications supplies both a .manifest and a .config file the settings in
the config file are completely ignored. When I remove the manifest file the
config file gets processed and vice versa. When both are present the config
file looses the battle.

To say it in front: The encoding of both files is UTF-8. There is no error
message, as it is the case, when the encoding schema does not match. This
was discussed in newsgroups very often and can be solved easily. But there
is no answer to my problem on the web today, or I have not found it.

I have already done some investigation on this subject. The problem does not
occur, when the application is started via a maped path like:

net use h: \\server\share
and then run with
h:\programs\application\app.exe

with
app.exe.config
app.exe.manifest
app.exe
located in directory \\server\share\programs\application

BUT NOT WHEN STARTED LIKE THIS:

\\server\share\programs\application\app.exe (config file gets ignored!!!!!)

Any help workaround or explanation why this happens would be very
appreciated.

Thanks
Th. Klein
Jul 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I forgott to mention that the same problem exists when the manifest file is
added to the exe as a resource as explained in the following msdn article:

URL:
http://msdn.microsoft.com/library/en...rame=true&_r=1
I hope someone could help me!

Thilo

"Thilo Klein" <ml****@hotmail.com> wrote in message
news:eC**************@TK2MSFTNGP11.phx.gbl...
Hi,
I have a managed app running from an unc path on the local intranet (Full
trust is set for this path with the .NET Configuration mmc!). If the
applications supplies both a .manifest and a .config file the settings in
the config file are completely ignored. When I remove the manifest file the config file gets processed and vice versa. When both are present the config file looses the battle.

To say it in front: The encoding of both files is UTF-8. There is no error
message, as it is the case, when the encoding schema does not match. This
was discussed in newsgroups very often and can be solved easily. But there
is no answer to my problem on the web today, or I have not found it.

I have already done some investigation on this subject. The problem does not occur, when the application is started via a maped path like:

net use h: \\server\share
and then run with
h:\programs\application\app.exe

with
app.exe.config
app.exe.manifest
app.exe
located in directory \\server\share\programs\application

BUT NOT WHEN STARTED LIKE THIS:

\\server\share\programs\application\app.exe (config file gets ignored!!!!!)
Any help workaround or explanation why this happens would be very
appreciated.

Thanks
Th. Klein

Jul 21 '05 #2

P: n/a
I forgott to mention that the same problem exists when the manifest file is
added to the exe as a resource as explained in the following msdn article:

URL:
http://msdn.microsoft.com/library/en...rame=true&_r=1
I hope someone could help me!

Thilo

"Thilo Klein" <ml****@hotmail.com> wrote in message
news:eC**************@TK2MSFTNGP11.phx.gbl...
Hi,
I have a managed app running from an unc path on the local intranet (Full
trust is set for this path with the .NET Configuration mmc!). If the
applications supplies both a .manifest and a .config file the settings in
the config file are completely ignored. When I remove the manifest file the config file gets processed and vice versa. When both are present the config file looses the battle.

To say it in front: The encoding of both files is UTF-8. There is no error
message, as it is the case, when the encoding schema does not match. This
was discussed in newsgroups very often and can be solved easily. But there
is no answer to my problem on the web today, or I have not found it.

I have already done some investigation on this subject. The problem does not occur, when the application is started via a maped path like:

net use h: \\server\share
and then run with
h:\programs\application\app.exe

with
app.exe.config
app.exe.manifest
app.exe
located in directory \\server\share\programs\application

BUT NOT WHEN STARTED LIKE THIS:

\\server\share\programs\application\app.exe (config file gets ignored!!!!!)
Any help workaround or explanation why this happens would be very
appreciated.

Thanks
Th. Klein

Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.