Window Callout

Verify your exefiles as save (apply to be a allowed puplisher) or tell IE any other way that these and only just these exe files aresave to open.

Why are these exe in the first place running content in IE. You know that this a situation that you normally do not want to have.

Any chance you can reprogram into Flash player or something?

just a thought.

W.

Thank you for the inputs. Our basic outputs are compiled as standalone EXEs that have to be platform independent. The content will be hosted in an intranet network and the client otherwise will fully trust our product. It is just that these callouts will be nagging the users. Any suggestion of the method of verifying the EXEs, will be helpful. Like, is it possible to verify content at the EXE level? I came across somewhere that signed activex could achieve this. Is that possible?

What you are trying to do with exe's is NOT SCORM compliant and would cause massive security headaches to IT people trying to protect their networks behind their firewalls.

In a nutshell your content has to be xml based and accessed with javascript based API's. See here for a primer.

There's no way I'd allow your exe's into my network.

Hooker

I dont think that there is any restriction in EXE's being there in a SCORM based content. Cant the content be SCORM compliant (with xml and javascript) and have links within, that call EXEs. If the network / users trust the source, why should there any issue! But how can yesyen avoid the default IE prompts???

I'm certainly not an expert on SCORM but the very premise of launching executables from remote (or even internal ) servers is usually the reason these specs are developed; ie, to provide a safe and secure methodology to transfer and display content.

While the SCORM spec does not say you "cannot" use exe's, it is very clear on what is to be used:

"SCORM specifies that content should:

• Be packaged in a ZIP file.
• Be described in an XML file.
• Communicate via JavaScript.
• Sequence using rules in XML."

This is taken from the link I provided above. All of the listed requirements clearly shows that the intent is to run from within the browser environment. Executing an exe on the client machine would require that the client OS be exposed to the application and any related data. This, IMO, destroys the intent of the standard and opens up the client, its operating system and its network to abuse.

In other words, the IE prompts are a protection device. Why should a user want to avoid them?

Hooker

This is not the windows call out but ''System Security'' setup to warn you that the opening / running of this file may be dangerous for your system. Think and confirm before you run it.

If you are sure that the site is safe you can configure to run without asking in Security

set up. See below:

Add your trusted site to avoid your problem

Have a fine day