Hi,

Im trying to get a c# 'applet' to work. Like demonstrated here:
http://samples.gotdotnet.com/quickstart/winforms/Samples/IeSourcing/VB/IESourcing.htm

but I can't get it running on my local server (so security should not be a
problem)
I tried simple examples like:
http://www.csharphelp.com/archives/archive109.html

but all I get is an empty object box.

I use Visual Studio 2003 and windows 2000 professional.
I there anything else I need to know?
Do I need to sign the assembly of something?
Do I need windows server to run a proper IIS.
Could a different internal-external IP be a problem?

thnx in advance,
Paul.

Re: c# applet by Paul

Paul
Thu Aug 28 17:51:39 CDT 2003

I got is working now. I had to set the permission of the virutal directory
to Scripts instead of Execute, which seems pretty weird to me. Is there a
reason for this?

This is from IIS help:
a.. Scripts Enables a script engine to run in this directory without having
Execute permission set. Use Script permission for directories that contain
ASP scripts, Internet Database Connector (IDC) scripts, or other scripts.
Script permission is safer than Execute permission because you can limit the
applications that can be run in the directory. If a client sends a request
to run a script in a folder that does not have Scripts permission, the Web
server returns an error. By default, all directories created during setup
have Scripts permission.
a.. Execute Enables any application to run in this directory, including
script engines and Windows 2000 binaries (.dll and .exe files). For security
purposes, do not give content folders Execute permission.

Paul.


"Shrawan" <shrawan.kumar@accenture.com> wrote in message
news:001a01c36d76$d8c9acd0$a301280a@phx.gbl...
> Hi,
>
> Could u please try changing the setting of u'r IE. Try
> changing it to default setting & try whether it works.
> The problem might be it is not downloading the control to
> u'r local computer.
>
> -Shrawan
>
> >-----Original Message-----
> >Hi,
> >
> >Im trying to get a c# 'applet' to work. Like demonstrated
> here:
> >http://samples.gotdotnet.com/quickstart/winforms/Samples/I
> eSourcing/VB/IESourcing.htm
> >
> >but I can't get it running on my local server (so
> security should not be a
> >problem)
> >I tried simple examples like:
> >http://www.csharphelp.com/archives/archive109.html
> >
> >but all I get is an empty object box.
> >
> >I use Visual Studio 2003 and windows 2000 professional.
> >I there anything else I need to know?
> >Do I need to sign the assembly of something?
> >Do I need windows server to run a proper IIS.
> >Could a different internal-external IP be a problem?
> >
> >thnx in advance,
> >Paul.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >.
> >



Re: c# applet by Jerry

Jerry
Thu Aug 28 19:42:16 CDT 2003

The reason is that when IE requests the applet DLL IIS tries to execute that
DLL as an ISAPI extension on the server. Once you tell IIS not to do that
(by setting the execute to scripts only or not allowing execution at all)
IIS will simply send the DLL to the client.

Jerry

"Paul" <anonymous@anonymous.com> wrote in message
news:3f4e86b8$0$49114$e4fe514c@news.xs4all.nl...
> I got is working now. I had to set the permission of the virutal directory
> to Scripts instead of Execute, which seems pretty weird to me. Is there a
> reason for this?
>
> This is from IIS help:
> a.. Scripts Enables a script engine to run in this directory without
having
> Execute permission set. Use Script permission for directories that contain
> ASP scripts, Internet Database Connector (IDC) scripts, or other scripts.
> Script permission is safer than Execute permission because you can limit
the
> applications that can be run in the directory. If a client sends a request
> to run a script in a folder that does not have Scripts permission, the Web
> server returns an error. By default, all directories created during setup
> have Scripts permission.
> a.. Execute Enables any application to run in this directory, including
> script engines and Windows 2000 binaries (.dll and .exe files). For
security
> purposes, do not give content folders Execute permission.
>
> Paul.