Hi Julie,
My apologies, please see the test case attached.
Thank you!
Can you please attach a small reproducible test case as per https://wisej.com/support/question/forum-guidelines
Delete the bin and obj folders before posting. We will try to reproduce from your test case and go from there.
Thanks,
Julie
Hi Rene,
we still cannot reproduce the issues that you reported.
Can you please try running your sample in a different browser or in incognito mode in Chrome to see if that makes a difference?
Best regards
Frank
Hello,
There are a couple of things that could be causing this issue and it’s hard to say for sure which one without seeing a test case. If none of these work, please upload a simple test case that reproduces the issue and I’ll have a look.
Try these things:
1. It could be a clean/rebuild issue, caused by renaming the project or changing the namespace. To fix it, delete the bin and obj folders, then rebuild.
2. Verify that Program.cs looks like this:
namespace SeaPass
{
static class Program
{
[STAThread]
static void Main()
{
Application.MainPage = new MainPage();
}
}
}
3. Open the .csproj file and confirm that the AssemblyName is SeaPass.
4. Verify that your default.json looks like this:
{
"url": "Default.html",
"startup": "SeaPass.Program.Main, SeaPass"
}
5. It could be an IIS issue, might be loading an old DLL. Try this: Stop app pool, deploy, delete old files, start app pool again
Hope this helps,
Julie
Adding a second web.config file in the Pdfjs subfolder works. We put our application webconfig back to the original state and removed the static content section from it to move it to a 2nd webconfig.
This is what the 2nd webconfig file inside the pdfjs subfolder looks like:
<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
<system.webServer>
<handlers>
<remove name=”json” />
</handlers>
<staticContent>
<remove fileExtension=”.mjs” />
<mimeMap fileExtension=”.mjs” mimeType=”application/javascript” />
<remove fileExtension=”.wasm” />
<mimeMap fileExtension=”.wasm” mimeType=”application/wasm” />
<remove fileExtension=”.ftl” />
<mimeMap fileExtension=”.ftl” mimeType=”application/octet-stream” />
<remove fileExtension=”.json” />
<mimeMap fileExtension=”.json” mimeType=”application/json” />
</staticContent>
</system.webServer>
</configuration>
Hi Edmond,
by commenting out that line you’re exposing your default.json settings file and any other json files that you might have and that contain sensitive data.
I’d recommend to either add a second web.config inside the pdf folder with the json or allow just that one specific json file in your main web.config.
Best regards
Frank
Hi Julie,
Thanks for checking.
I’m using Wisej 4.1.0-beta.39 (runtime build 4.1.0.39), on .NET Framework 4.8.1, running under IIS Express, tested in Chrome on Windows. It’s the same sample I sent you, with the NuGet package set to 4.1.0-beta.39.
I’ve attached a video showing it: I first switch between several themes and perform a few actions — those respond fast. Then I switch to the Fluent theme and you can see the response becomes clearly slower for the same actions.
Steps in the video: build & run the sample, use the dropdown at the top to switch themes, and interact with the controls after each switch to compare the responsiveness.
Please let me know if you need anything else to reproduce it.
Thanks
Hello,
I tested with your sample and I am unable to reproduce. What version of Wisej are you using? Can you attach a video of you reproducing the issue?
Thanks,
Julie
For Wisej 3.5 you need to target net48 to get the designer to work, However, that is no longer necessary in Wisej 4.0.
You can use ..NET 8 9 or 10 in visual studio 2026. Your TargetFrameworks in your .csproj should look like this: net9.0-windows;net9.0 The -windows target is necessary for the designer to work.
For resolving the “WisejHandler not found” error, try to create a brand new Wisej 4 .NET 8, 9 or 10 project and compare its Program.cs and csproj to your old project. If that doesn’t work, attach a small test case the reproduces the issue and we can take a look.
Hope this helps,
Julie
Please contact support at supportATiceteagroup.com. We cannot publish this information on the internet, but would be happy to assist you there.
Thanks Frank.
As a temporary workaround, I used a JavaScript MutationObserver to replace the incorrect Portuguese translation "Claro" with "Limpar" when the filter popup is created.
Example workaround:
private void Window1_Load(object sender, EventArgs e)
{
LoadData();
dataGridView1.AllowColumnFilter = true;
this.Eval(@"
const observer = new MutationObserver(function() {
document.querySelectorAll('a').forEach(function(a) {
if (a.textContent.trim() === 'Claro') {
a.textContent = 'Limpar';
}
});
});
observer.observe(document.body, {
childList: true,
subtree: true
});
");
}
I am also attaching a small Wisej 4 sample project in case it helps others reproduce the issue.
Hopefully this helps anyone facing the same Portuguese translation problem until the official fix is included in the next Wisej.NET release.
Regards, Paul
Hi Ruben,
it should be clear.Text in SimpleColumnFilterPanel.pt.resx
We will change it for the next Wisej.NET releases.
Best regards
Frank
Hi again, i must apology: my license is only vaid for one activation and i changed the Raspberry hardware and sd card so this was my problem.
Hi Paul,
this has been reported and fixed and will be deployed with the 4.0.12 release.
As a workaround please use 4.0.12-preview2 on nuget.org
Best regards
Frank
Hi Nico,
please send your license key to support@wisej.com and we’ll take a look.
Best regards
Frank
Ok, with Application.Update() the enable/disable works. But as we wanted handle this globally, we resolved this by creating our own event handler which wraps the original one using reflection. And in the wrapper event we using the enable/disable.
You can’t stop characters from the server. Use the Filter property (see docs and api) or a javscript event handler. It’s much better if you attach a zip file with the sample and runnable code. I don’t think anyone would like to type code snippets for you.
You’re correct that the call to Application.Update does not have to happen in the ViewModel.
Here’s a sample showing how to do async commands in Wisej MVVM.
– The async method should be in the ViewModel,
– Navigation or shell swapping should happen in an application-level ViewModel reacting to authentication state
– Any Wisej-specific Application.Update(…) usage should be hidden in infrastructure that restores/pushes the Wisej context rather than called from the ViewModel itself.
– In the sample, look at:
– LoginViewModel.cs for the async login logic
– ApplicationViewModel.cs for shell swapping (MainViewModel and LoginViewModel are the shells)
– WisejAsyncCommand.cs and WisejUiDispatcher.cs for the Wisej-aware command/context handling
– WisejUIDispatcher for the call to Application.Update
– Window1.cs for the shell host.
Dear Julie,
thanks for your answer.
So you mean in the definition of the LoginCommand in the ViewModel’s constructor:
However I find it a bit strange, in the sense I would expect my ViewModel to be unaware of Wisej’s Application.Current etc. What if I wanted to use the same ViewModel for a WinForms application and not a Wisej one?
Best regards,
Alex
Application.Update(this) works when this is a Wisej control. But in your case, this is the ViewModel. So don’t use Application.Update(this). Instead, you can save the context before the await by doing:
var context = Application.Current.
Then when you need to update the UI you can do:
Application.Update(context);
More information on Application.Current: https://docs.wisej.com/api/wisej.web/general/application#current
