Manifest Files & VS2005

[John Bowman]

Hi All,

I originally sent this to the dotnet.security ng, but no repsonse in 5 days.
Hopefully, someone here can explain to me what's going on.
I'm fairly new to .NET app security and manifests. I'm working with a test
app: "MyApp.exe".

Couple Q's:

1) When I turn on the security project setting in VS2005 for "Enable
ClickOnce Security Settings" and then choose; " This is a full trust
application" (I realize normally we should not do that), when I compile the
app, it produces "MyApp.exe.manifest" & "MyApp.application" files. When I
look in the "Properties" folder in the Solution Explorer I can also see it
has an app.manifest file whose BuildAction is set to Embedded Resource. I'm
confused - if the manifest file is embedded into the assembly, why are the
two files mentioned above produced?

2) Also, if this were a releasing application for distribution, do I need to
include thiese 2 files with the distro if the manifest is really embedded?

3) If I choose "This is a partial trust application" and then include some
special permissions, ILDASM seems to show the exactly the same mainfest
information as when it's a full trust app. That said, the app.manifest file
shown in the VS2005 Solution Explorer appears to record the permission
changes, but I can't find them in ILDASM. What's going on here? Please
educate me.

TIA,
--
John C. Bowman
Software Engineer II
Thermo Fisher Scientific
<Remove this before replyjo*********@thermofisher.com
WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of
this e-mail or the information herein by anyone other than the intended
recipient, or an employee or agent of a system responsible for delivering
the message to the intended recipient, is prohibited. If you are not the
intended recipient, please inform the sender and delete all copies.

[Chan Ming Man]

Have you taken a look on this:
http://msdn2.microsoft.com/en-us/library/76e4d2xw.aspx

chanmm

"John Bowman jo*********@thermo.com>" <<Remove this before replywrote in
message news:Oz****************@TK2MSFTNGP03.phx.gbl...

Hi All,

I originally sent this to the dotnet.security ng, but no repsonse in 5
days. Hopefully, someone here can explain to me what's going on.
I'm fairly new to .NET app security and manifests. I'm working with a test
app: "MyApp.exe".

Couple Q's:

1) When I turn on the security project setting in VS2005 for "Enable
ClickOnce Security Settings" and then choose; " This is a full trust
application" (I realize normally we should not do that), when I compile
the
app, it produces "MyApp.exe.manifest" & "MyApp.application" files. When I
look in the "Properties" folder in the Solution Explorer I can also see it
has an app.manifest file whose BuildAction is set to Embedded Resource.
I'm
confused - if the manifest file is embedded into the assembly, why are the
two files mentioned above produced?

2) Also, if this were a releasing application for distribution, do I need
to
include thiese 2 files with the distro if the manifest is really embedded?

3) If I choose "This is a partial trust application" and then include some
special permissions, ILDASM seems to show the exactly the same mainfest
information as when it's a full trust app. That said, the app.manifest
file
shown in the VS2005 Solution Explorer appears to record the permission
changes, but I can't find them in ILDASM. What's going on here? Please
educate me.

TIA,
--
John C. Bowman
Software Engineer II
Thermo Fisher Scientific
<Remove this before replyjo*********@thermofisher.com
WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of
this e-mail or the information herein by anyone other than the intended
recipient, or an employee or agent of a system responsible for delivering
the message to the intended recipient, is prohibited. If you are not the
intended recipient, please inform the sender and delete all copies.