I previously reported this issue, and it can be resolved by updating to the latest preview version.
Please see here:
https://wisej.com/support/question/chinese-text-autosize-issue-in-wisej-4
I want to emphasize once again that Wisej is the best cross-platform framework I’ve ever used.
Please find VS project in attachment zip file.
VS Extend version: 4.0.2
Wisej framework nuget package version: Wisej-4 (4.0.2 stable version and 4.0.3 preview 17)
I have tried to run same project with Wisej-3.5, it is better than Wisej-4, Chinese text of CheckBox and RadioButton can be fully shown. But text still wrap.
Text wrap is also a critical problem because Chinese language also need some charactor combination to explain some meaning.
For example: “确定” means “Ok”, but it is shown in Button as :
确
定
Just like english
O
k
It seems very strange.
And another bug to report:
A control (such like a button) locates in TableLayoutPanel which has a couple of cells, while pressing Ctrl key, and use mouse left button to drag it from a cell to another cell, I expect to clone a control in target cell. But a error (index duplicated) will occur actually. But if drag it to a location not in this TableLayoutPanel, it will be performed normally.
This bug is in both Wisej-3.5 and Wisej-4.
Hello Julie,
I didn’t say that no binding source is created, but that the wrong BS is created.
Wisej.Web.Bindingsource != System.Windows.Forms.Bindingsource
The following occurs when creating a Wisej.Web.Bindingsource manually
– Add a Wisej.Web.Bindingsource to the page
– In the properties of the binding source, I want to set the binding
– I select my class
– The selected class is not applied, remains at (none).
I would like to revise my previous statement regarding the datagrid. Very strange things happen when trying to change the datasource. In my opinion, there are still fundamental designer problems with binding via a bindingsources.
Sven
What version of Wisej are you using?
Please attach a reproducible test case. Delete the bin and obj folders before posting.
It’s not true that the binding source cannot be created. It’s created as System.Windows.Forms and only when binding from the (DataBinding) section. In any case, you can replace the class name by hand.
I came across a thing that may be useful in this way. Uninstalled VSIX, reinstalled it, opened VS and my designer instance and boom …. this error: “Message from web page” (error title) , “Renderer callback failure: class does not support automation.”.
Can this have any relations with our current issue?
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.
Hi Jean,
please contact us at supportATwisej.com with both your developer and server license key.
Best regards
Frank
I can reproduce, we are looking into fixing this.
Julie
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
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
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.
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
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
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
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
