All Answers

Any template works out of the box. Hit run and it works. To publish to IIS you need to follow Microsoft instructions. These are all standard ASP.NET or ASP.NET Core apps. Or pick your target here https://docs.wisej.com/deployment and follow the steps. The most common error that people new to Microsoft ASP.NET Ccore make is to create the wrong target, fail to install the correct IIS plugin, configure web.config incorrectly (see commenter section).

Publishing on Azure, AWS, etc. are all standard ASP.NET or ASP.NET Core.

If you post what you are trying to deploy (net48 is ASP.NET, netcore is ASP.NET Core) and how (what steps are you following) and what error you are getting) someone may be able to help you.

See https://docs.wisej.com/deployment

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:

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:

• The Application Pool targets .NET CLR Version v4.0.
• The site is configured as an application, not a virtual folder.
• web.config is present in the root folder.

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:

<script src="wisej.wx"></script>
(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”

Try clearing your browser cache. If that doesn’t fix the issue, post a compliable test case with the bin and obj folders removed and we will investigate.

Here is the updated web.config file

I included the full file as well as the snippet you can paste into your web.config file. I would recommend pasting in the snippet so that you can keep your current settings.

Look into using Wisej AI. In order to get the nuget package for it, you will need to be a Technology Partner. Here’s a link to the quick start guide in the Wisej.AI documentation: https://docs.wisej.com/ai/concepts/getting-started

When I update my Web.config to your example, the application won’t run on my local machine.

Is this only for deployed applications?

See this forum post: https://wisej.com/support/question/disable-back-button-on-browser

You do not need to downgrade anything or find version 4.0.1.2.
You simply have to add (or verify) a binding redirect in your web.config so that all components use the newer version.

Example web.config snippet is attached

If this doesn’t work, please post a compliable test case with the bin and obj folders removed and we’ll investigate further.

how do I execute your suggestion:

dotnet publish -c Release -r win-x86 –self-contained true

?

Here are some things you can try:

1.Check the Event Viewer / stdout logs on the server
On your MochaHost deployment, go into your published folder.
In web.config, make sure you have logging enabled:
<aspNetCore processPath="dotnet" arguments=".\YourApp.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />
Create a logs folder in the root with write permissions.
Then try hitting your app again — it should generate a .log file with the real startup error.

2.Check the Target Runtime
Did you publish as Framework-Dependent or Self-Contained?
Shared hosting (like MochaHost) usually does not have .NET runtime pre-installed, or may not have the same version as your dev PC.
To be safe, publish as Self-Contained Deployment:
dotnet publish -c Release -r win-x86 --self-contained true
(or win-x64 depending on host environment)
Then upload the entire publish folder, including all .dlls and .exe.

3.Check for Missing Files
Sometimes FTP doesn’t push all files (especially hidden ones). Re-upload the publish folder fresh.
Make sure web.config is present.

4.Check .NET Version Compatibility
If you built with .NET 8, but MochaHost only supports up to .NET 6 (example), a framework-dependent app won’t run.
Either:
Switch your app’s target to a supported version in csproj.
Or deploy self-contained.

Unfortunately, there is no built in way to do this in Wisej. I would recommend that you transpose the data source.

You could manually do this with switching between a FlowLayoutPanel and a DataGridView, see attached example.

Yes, your development PC should cause a license activation. This is working as expected. Go to the wisej website (https://wisej.com/), click on support then account. Under “License Keys: click on “manage activations”. You can then deactivate your additional activations.

So first off, make sure that you’re changing the properties of the Switch, not of the Checkbox. The appearance is controlled by Switch.

Next, if you look closely at the Switch properties, under “Icon” there are several options- Default, Checked, Undetermined, and Hovered. You can set the knob color for each. The knob is actually a pseudo element added with css under the switch appearance. So you need to edit the css.

Here’s an example of what the JSON looks like for setting the knob color to red for the “checked” state

"switch": {
"components": {
"icon": {
"checked": {
"styles": {
"color": "transparent",
"css": "{\"overflow\":\"visible !important\",\":before\":{\"content\":\"\",\"width\":\"18px\",\"height\":\"18px\",\"border-radius\":\"20px\",\"background-color\":\"red\",\"position\":\"absolute\",\"top\":\"-4px\",\"left\":\"22px\",\"transition\":\"left 100ms\"}}"
}
}
}
}
}

I’ve also attached a screenshot of how to change it in the Theme Builder.

Wisej has nothing to do with System.IO. It’s a Microsoft library.

https://stackoverflow.com/questions/73435207/system-platformnotsupportedexception-system-io-ports-is-currently-only-supporte

Thank you for the video.  I watched, followed your instructions; when I got into New Project in VS 2022, there is NO wisej 4 option, only Wisej 3

Never mind, I re-ran the vsix and managed extensions, and re-installed 4 and exited VS, reentered VS, started a new project and it was there!  🙂  thanks

You’ll need to install the Wisej 4 VSIX: https://wisej.com/builds/

If you’re not sure if Wisej 4 is installed, you can check by opening Visual Studio, going to Extensions -> Manage Extensions, and clicking on the “installed” tab. There you should see all the versions of Wisej that you have installed.

Then when you are creating a new project, select “Wisej 4” from the dropdown. See attached picture.

See also this video: https://www.youtube.com/watch?v=tpqSI2OfrBA

Hope this helps,

Julie

This is an issue caused by having multiple versions of Wisej installed side-by-side (in your case Wisej 3.5 and Wisej 4).

Visual Studio tries to load the design-time component assemblies, and if it picks up the wrong version (or a mix of 3.5 and 4), you’ll see “Failed to create component…” when dragging from the toolbox.

How to fix it:

1. Try cleaning and rebuilding your project, restarting Visual Studio, restarting your computer and cleaning and rebuilding your project again.
2. Clear the cache- Visual Studio caches assemblies for the toolbox and designer. Close Visual Studio, then delete the contents of these folders:
   C:\Users\<YourUsername>\AppData\Local\Microsoft\VisualStudio\<version>\ComponentModelCache
   C:\Users\<YourUsername>\AppData\Local\Microsoft\VisualStudio\<version>\Designer\ShadowCache
3. Check your project references- open your .vbproj file by double-clicking on the project name in the Solution Explorer. Double-check that it is referencing Wisej 4 (Should look like this: <PackageReference Include=”Wisej-4″ Version=”4.0.*-*” />) and not Wisej 3.5
4. Try temporarily uninstalling Wisej 3.5 (uninstall it from Visual Studio → Extensions → Manage Extensions)
5.  Reset the toolbox- Go to the Tools menu → Import and Export Settings. Select Reset all settings → click Next. You can choose Yes, save my current settings (optional) or No. Pick your default environment (e.g., VB or C#). This will rebuild the toolbox from scratch.

Hope this helps,

Julie

There’s a VirtualKeyboard API https://developer.mozilla.org/en-US/docs/Web/API/VirtualKeyboard/show but it’s only compatible with Chromium based browsers.