Serving javascript

  • I have an ISAPI DLL that outputs code that links in a js file and a css file. This makes devlopement much easier since I can change much of the web application by altering the javascript and the css instead of the DLL C code. On one PicoCom (my own development version), this works without any problems.


    But on another PicoCom only the HTML from the ISAPI DLL is served and neither the javascript nor the css, in fact not even a header image (a gif file) is correctly being served by the web server. Needless to say, all the files do exist and are in the correct folders.


    I get nothing sensible from Chrome and/or Firefox that could help me. For instance, all Chrome says is 'Unexpected > at line 1' which doesn't make sense at all.


    Strangely enough, SysAdmin (and WebAdmin) both work fine on both systems but they don't rely on exterenal files.


    Any ideas shedding light on this baffling problem are VERY welcome.


    Regards,
    Dag Hovden

  • Hello,
    please refer HKLM\Platform. Are the System SW the same on both PicoCOM? Maybe some OS features are missed on the "not working" PicoCOM.


    Quote

    ...(my own development version)...

    Did you use BSP for create own kernel?

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • One of the systems (my dev system) is Pro and the other is Core so, yes there's a difference. But they both have the IIS web server and I don't really see why the Pro components (Internet Explorer, Media Player, etc) should make a difference in IIS's serving of javascript and css.

  • Hello,
    definitely the OS componets are the reason for failure.

    Quote

    I don't really see why the Pro components (Internet Explorer, Media Player, etc) should make a difference ...

    When you select one OS component in most cases a lot of dependencies are added automatically. We can be sure that such a dependency is missed in the "not working" image.


    Which two image bin-files do you use?
    OS features a listed under \windows\ceconfig.h. Is there an apparent difference (e.g. jscript) in these files concerning your problem.

  • Figured this one out eventually and it had nothing to do with the Windows Image version. What happened was that I had two VROOT definitions, / and /MyApp, both pointing to myisapi.dll. This was a pure oversight (I started with / and decide to do /MyApp instead later) and caused all kind of strange problems since referring to '/anything' in my HTML would trigger the / VROOT instead.