All Answers

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.

Try updating to 4.0.2, that should fix the issue

Julie

Hi Dino,

You don’t need to install libgdiplus if you’re using aspnet:8.0 as your base image:

Please use this docker file instead:

#See https://aka.ms/containerfastmode to understand how Visual Studio uses this Dockerfile to build your images for faster debugging.

FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base

#Install standard fonts
RUN echo “deb http://deb.debian.org/debian/ bookworm main contrib” > /etc/apt/sources.list && \
echo “deb-src http://deb.debian.org/debian/ bookworm main contrib” >> /etc/apt/sources.list && \
echo “deb http://security.debian.org/ bookworm-security main contrib” >> /etc/apt/sources.list && \
echo “deb-src http://security.debian.org/ bookworm-security main contrib” >> /etc/apt/sources.list
RUN sed -i’.bak’ ‘s/$/ contrib/’ /etc/apt/sources.list
RUN apt-get update; apt-get install -y ttf-mscorefonts-installer fontconfig

WORKDIR /app
EXPOSE 80
EXPOSE 443

ENTRYPOINT [“dotnet”, “WisejWebApplication17.dll”]

Best,
Alaa

Just for reference on installed versions:

root@4920570cb1a4:/app# apt-get install libgdiplus
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
libgdiplus is already the newest version (6.1+dfsg-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@4920570cb1a4:/app# apt-get install libfontconfig1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
libfontconfig1 is already the newest version (2.14.1-4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@4920570cb1a4:/app# apt-get install fontconfig
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
fontconfig is already the newest version (2.14.1-4).
fontconfig set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@4920570cb1a4:/app# apt-get install ttf-mscorefonts-installer
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
ttf-mscorefonts-installer is already the newest version (3.8.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I tried and was unable to reproduce. Can you please wrap up a small test case where I can reproduce the issue? Make sure to delete the bin and obj folders before posting.

Thanks,

Julie

Hi Alaa,

Last night or early this morning it happend again.

Am I to understand the license is checked every time the site is restarted even if no newer WiseJ our app version is published? If so, this means our apps are depended on your servers to be online? What happens if a license expires, will the app no longer work?

im running vs 17.14.16
Born with 3.5 and ported to 4.0 now 4.0.1
<TargetFrameworks>net481;net9.0</TargetFrameworks>

Hi Antonio,

Is this running with the latest VSIX ?

Is it Wisej.NET 3.5 or 4.0?

Best,

Alaa

It’s a permissions issue. If you’re using IIS you need to give IIS_USER read/write permission.

I just uninstalled the WiseJ extension and re-installed it. No error mentioned above, but still no Wisej controls in the toolbox.

I even created a new WiseJ project and it also did not have tools.

I’ve installed the .visx half a dozen times, including downloading new installers each time.  I even uninstalled the extension and re-installed it.

no happiness yet.

further advice?

Strangely enough…In one of my other TEST programs, the Wisej does show up in the Visual Studio design toolbox…  I can even copy a control from this application and paste it successfully in my new application. But, alas, the Wisej controls still do not show in the toolbox within.