All Answers

1 vote

Ok, if it is a problem with Visual Studio, that means that there is a conflict between VS and WiseJ. This is how I can understand it.
This problem is showing regularly when using .Net Core only without .Net Framework and this is the way to go for future, isn’t it?
Hours of the developer time are gone fixing over and over this trouble and this is remaining us to the start point before any time cut recommendation to use WiseJ.
You should consider this issue as a serious one if you really target a continuity in the market. This is an advice from a lover of your product where everything else is really shining.
However, if anyone need it, I normally solve that by closing any design instances + closing the toolbox panel + closing the VS itself.
Then go to the folder C:\Users\<YourOSUserNameHere>\AppData\Local\Microsoft\VisualStudio\17.0_00f65c2e.
In sub folder ComponentModelCache delete all files.
In sub folder \Designer\ShadowCache delete all files.
Reopen VS, load a designer instance (Form, User Control ….etc.) and reopen the ToolBox panel.
Thanks.

0 votes

Hi Jean,

please contact us at supportATwisej.com with both your developer and server license key.

Best regards
Frank

0 votes

I can reproduce, we are looking into fixing this.

Julie

0 votes

Hello Daniel,

A new FluentUI theme is currently in the works and will be released with a new minor release of Wisej.NET!

Best Regards,
Alaa

0 votes

Hi Harold,

Glad to hear it’s working on Google Play!

Can you try adding this to iOS?

<PropertyGroup Condition=”‘$(TargetFramework)’==’net9.0-ios'”>
<MtouchInterpreter>-all,Humanizer</MtouchInterpreter>
</PropertyGroup>

All optimizations and linking/trimming should be disabled.

You can also compare your configuration to our sample app that we deploy:

wisej-hybrid-examples/Showcase/App/HybridApp.csproj at 4.0 · iceteagroup/wisej-hybrid-examples

 

HTH,

Levie

0 votes

We found the cause of the issue. We tried with Ressource from FullCalendar
In newer versions of Wisej-3-FullCalendar (starting from around v3.5.13 nad continued in Wisej-4), the class
Wisej.Web.Ext.FullCalendar.Resource was renamed to ResourceScheduler.

That’s why projects that used new Resource() stopped compiling after the update.
The fix is simply to replace the old class and property with the new ones:

fullCalendar1.ResourceSchedulers = new Wisej.Web.Ext.FullCalendar.ResourceScheduler[]
{
new Wisej.Web.Ext.FullCalendar.ResourceScheduler { Id = “U1”, Title = “Anna Müller” },
new Wisej.Web.Ext.FullCalendar.ResourceScheduler { Id = “U2”, Title = “Ben Huber” }
};

Everything else —  works the same as before.

So the issue wasn’t missing references, just a renamed class in the newer builds.

0 votes

Hi John,

Like my colleague Julie pointed out, the latest Cumulative update (KB5066835) for Windows is what’s causing the issues you’re having.

It essentially made the IIS services not work, everything would work fine if you uninstall the update!

Best,
Alaa

0 votes

I tested your sample and it runs fine on my machine. So it’s an issue with your machine.

This is actually windows related, not Visual Studio related. You need to uninstall the KB5066835 update.

 

-Julie

0 votes

It might be possible with a custom view. FullCalendar is a third party extension, not created by us. You may find it helpful to read their documentation here: https://fullcalendar.io/docs

Can you provide more details- a link to something similar or a screenshot of what you are trying to do?

 

-Julie

0 votes

Wisej is not a web server. 404 or any other error code is managed by the web server.

For IIS: https://www.google.com/search?q=iis+handle+404

  • JD answered Oct 12, 2025 - 4:51 pm
0 votes

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?

 

0 votes

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.

0 votes

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.

0 votes

faild to load wisej.wx

0 votes

after publish i can’t find

Wisej.Web.dll

Wisej.Core.dll

0 votes

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 🙂 )

0 votes

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.

  • JD answered Oct 7, 2025 - 3:40 pm
0 votes

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.

 

 

  • JD answered Oct 7, 2025 - 3:38 pm
0 votes

Did you follow these steps?

https://docs.wisej.com/deployment

Which target exactly?

 

  • JD answered Oct 7, 2025 - 3:33 pm
0 votes

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.

 

 

 

 

  • JD answered Oct 7, 2025 - 3:29 pm
  • last active Oct 7, 2025 - 3:30 pm
Showing 21 - 40 of 11k results