Wisej is not a web server. 404 or any other error code is managed by the web server.
I created a small .aspx website; published it successfully; it runs successfully, apparently starting with default.aspx.
I use the exact same publish settings from Visual Studio 2022; it publishes successfully; but when I enter my https://subdomain.domain.org, it always fails with a blank screen or various errors.
It appears there is no “default.aspx” entry point for the application.
…after researching, I have created my application with wiseJ windows…are these NOT deployable as a website?
It’s a Visual Studio problem- not caused by Wisej. If it happens again, do this:
Open the designer (no tools). Recompile. Close the designer. Close VS. Reopen VS. Open the designer. If it doesn’t work, right click on the toolbox, reset toolbox. Close designer. Close VS. Reopen.
I can’t find an update toolbox option anywhere. Still no Wisej options in the toolbox.
If I create a new Wisej project with just one window, they are there.
If I add my project to the newly created project that is working, then my windows show all of my Wisej controls, but the toolbox still has no Wisej controls for that window even though there are many installed in the window.
In the attached screen capture, you can see the button properties beside the toolbox for that window. The page displays fine, but I can’t add any Wisej controls to it because they are not “available”
I downloaded and re-installed Visual Studio 2022; re-downloaded and reinstalled the Wisej 4 vsix. No improvement.
faild to load wisej.wx
after publish i can’t find
Wisej.Web.dll
Wisej.Core.dll
I followed the video instructions exactly and it failed with System.Windows.forms must be installed.
In order for this error to be resolved, I upgraded the .net from 7.0 to 8.0 and it compiled and ran.
I’ll try to deploy and let you know my success (I hope 🙂 )
You can also use Microsoft SK with Wisej. It’s just plain .NET. There are many samples available, just copy the code and it will work.
If you are using net9 there is no version mismatch usually. If you are using net48 you may have to normalize the versions of the different libraries you are importing. It’s very common.
This is how to do it: https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions
It’s quite simple. I usually go for “0.0.0.0-9.9.9.9” to bind to the unified version.
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.
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:
<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
?