Julie (ITG) answered 2025-10-07 14:16:19 UTC

wisej.wx

is the core JavaScript file automatically served by Wisej. It’s not a static file — Wisej generates and serves it dynamically at the endpoint:

/wisej.wx

So, if that request fails (404, 500, or blocked), the browser cannot start the app UI.

If you go to https://bestgen.runasp.net/wisej.wx you'll get a 500 error. If it's working, you should see some JS code.

Check these things:
**1.

web.config

exists and is deployed**

Ensure

web.config

is in the same directory as

Default.html

Make sure you did a Publish (not just copy

bin/

manually).

Do not rename or move

wisej.wx

2. The site is set as an Application in IIS

Make sure the Wisej app is deployed as a .NET web application, not just HTML files.

In IIS, check:

3. Default.html references wisej.wx relatively

If your app is hosted in a subfolder, e.g.
https://myserver.com/testapp/
but the HTML still references /wisej.wx (absolute path), the browser will request
https://myserver.com/wisej.wx (root path) — and it fails.

Fix:

In Default.html, make sure the script is:

(relative path, not starting with a slash)

**4. Wisej assemblies exist in

bin/

Ensure these DLLs exist on the server:

Wisej.Framework.dll

Wisej.Web.dll

Wisej.Core.dll

5. No trimming or single-file publish

In Visual Studio, Publish → Settings → File publish options

Check “Remove additional files at destination”

Uncheck “Trim unused assemblies”

publish project not load on host #4880

Description