No Touch Deployment Warnings

When our smart client is loaded thru the browser, there is a balloon that
pops up with the following warning:

Microsoft .NET Security Information
This application is running in a paritally trusted context. Some
functionality in the application may be disabled due to security
restrictions.

The application works great and is doing everthing it is intended to. The
message is annoying and our client is complaining about it.

My question is that I want to know if there is a way to disable this without
touching the default security settings in the .NET Framework 1.1
Configuration app. The point is not to have the client have to download
anything extra to install or have them modify anything. How is this no
touch deployment if you do?

Thanks

Greg
Thu Jan 22 12:15:29 CST 2004

Your app is running in a secure sandbox (Internet or Intranet). That is why
you see the warning. The warning is a good thing.

You can create your own custom code group and distribute a .msi that creates
the code group or an exe that creates the code group. Take a look at CAS
and Code Groups (Membership, Permission Sets) to learn more about this.
"Ben S. Stahlhood II" <ben[.dot.]stahlhood[.at.]intellified[.dot.]com> wrote
in message news:u0pBE8Q4DHA.1752@tk2msftngp13.phx.gbl...
> When our smart client is loaded thru the browser, there is a balloon that
> pops up with the following warning:
>
> Microsoft .NET Security Information
> This application is running in a paritally trusted context. Some
> functionality in the application may be disabled due to security
> restrictions.
>
> The application works great and is doing everthing it is intended to. The
> message is annoying and our client is complaining about it.
>
> My question is that I want to know if there is a way to disable this
without
> touching the default security settings in the .NET Framework 1.1
> Configuration app. The point is not to have the client have to download
> anything extra to install or have them modify anything. How is this no
> touch deployment if you do?
>
> Thanks
>
>

Jose
Fri Jan 23 07:02:25 CST 2004

I am facing the same issue and I think is NOT a good thing.

jc


"Greg" <greg@cds-am.net> wrote in message
news:uOnQRPR4DHA.360@TK2MSFTNGP12.phx.gbl...
> Your app is running in a secure sandbox (Internet or Intranet). That is
why
> you see the warning. The warning is a good thing.
>
> You can create your own custom code group and distribute a .msi that
creates
> the code group or an exe that creates the code group. Take a look at CAS
> and Code Groups (Membership, Permission Sets) to learn more about this.
> "Ben S. Stahlhood II" <ben[.dot.]stahlhood[.at.]intellified[.dot.]com>
wrote
> in message news:u0pBE8Q4DHA.1752@tk2msftngp13.phx.gbl...
> > When our smart client is loaded thru the browser, there is a balloon
that
> > pops up with the following warning:
> >
> > Microsoft .NET Security Information
> > This application is running in a paritally trusted context. Some
> > functionality in the application may be disabled due to security
> > restrictions.
> >
> > The application works great and is doing everthing it is intended to.
The
> > message is annoying and our client is complaining about it.
> >
> > My question is that I want to know if there is a way to disable this
> without
> > touching the default security settings in the .NET Framework 1.1
> > Configuration app. The point is not to have the client have to download
> > anything extra to install or have them modify anything. How is this no
> > touch deployment if you do?
> >
> > Thanks
> >
> >
>
>

wozza96
Sun Feb 08 16:06:31 CST 2004

I agree. It is frightening and confusing for my users (all of whom are
on a LAN and running this thing in intranet zone)

"Jose Caliente" <jc@noble.net> wrote in message news:<OHprkEb4DHA.1948@TK2MSFTNGP12.phx.gbl>...
> I am facing the same issue and I think is NOT a good thing.
>
> jc
>
>
> "Greg" <greg@cds-am.net> wrote in message
> news:uOnQRPR4DHA.360@TK2MSFTNGP12.phx.gbl...
> > Your app is running in a secure sandbox (Internet or Intranet). That is
> why
> > you see the warning. The warning is a good thing.
> >
> > You can create your own custom code group and distribute a .msi that
> creates
> > the code group or an exe that creates the code group. Take a look at CAS
> > and Code Groups (Membership, Permission Sets) to learn more about this.
> > "Ben S. Stahlhood II" <ben[.dot.]stahlhood[.at.]intellified[.dot.]com>
> wrote
> > in message news:u0pBE8Q4DHA.1752@tk2msftngp13.phx.gbl...
> > > When our smart client is loaded thru the browser, there is a balloon
> that
> > > pops up with the following warning:
> > >
> > > Microsoft .NET Security Information
> > > This application is running in a paritally trusted context. Some
> > > functionality in the application may be disabled due to security
> > > restrictions.
> > >
> > > The application works great and is doing everthing it is intended to.
> The
> > > message is annoying and our client is complaining about it.
> > >
> > > My question is that I want to know if there is a way to disable this
> without
> > > touching the default security settings in the .NET Framework 1.1
> > > Configuration app. The point is not to have the client have to download
> > > anything extra to install or have them modify anything. How is this no
> > > touch deployment if you do?
> > >
> > > Thanks
> > >
> > >
> >
> >

rcreddych
Tue Feb 10 03:25:58 CST 2004

If we need to change the default internet settings in the client
machine, how can we call it as No Touch Deployment? We should call it
as Low Touch Deployment!!! Think, if 3rd party components are used in
the assembly.