All Answers

Hi Mo,

you don’t need a separate license for 4.0. If you’re using a valid 3.5 license you can apply the same key to your 4.0 installation.

Best regards
Frank

I have created a small project but the issue is still there expecially when assigning a property from code behind to the interface.

Hi,

I have read that document but extern alias do not seem to work.

(see attached screenshot)

Have you got any hints?

Thanks

Luca

It’s explained here:

https://docs.wisej.com/docs/whats-new-in-4.0/managed-graphics#namespace-collision

Just to add details: using PdfSource instead of PdfStream is even worse, just a “cannot load plugin” is displayed in the center of PdfViewer.

public static void DisplayPDF(byte[] pdfBytes, Page returnPage = null, string title = “”)
{
string nf=GenerateName(10) + “.pdf”;
string url = Application.Url + $”temp/{nf}”;
string path = Path.Combine(Application.StartupPath, “temp”, nf);
if (!Directory.Exists(Path.Combine(Application.StartupPath, “temp”))) Directory.CreateDirectory(Path.Combine(Application.StartupPath, “temp”));
File.WriteAllBytes(path, pdfBytes);
var f = new Page();
if (returnPage != null) AddReturnFloatingButton(f, returnPage);
Application.Title = title;
Wisej.Web.PdfViewer v = new PdfViewer();
v.Dock = DockStyle.Fill;
v.PdfSource = url;
v.FileName = title;
v.ViewerType = PdfViewerType.Auto;
f.Controls.Add(v);
f.Show();
}

I have a similar issue in WiseJ 4.0. As soon as I change the JSON of the Options property (for example just changing the zoom level) the map turns grey at runtime (at design time everything works fine). I don’t get any relevant erros in the console. Any suggestions?

Hi Frank,

Thanks for your comment about it.

In checking version 3.5.18, the majority of standard controls can be dragged into TableLayout perfectly. I only found an issue when a MonthCalendar is dragged in. The control has glitches in design mode.

The video attached shows the issue.

Best regards, Paul

Hello,

Try restarting Visual Studio, this should fix the issue and load the Wisej controls.

Julie

Hi,

this is fixed in Wisej.NET 3.5.18 that has been deployed today.

Best regards
Frank

Hi Paul,

Wisej.NET 3.5.18 has been released that fixes this issue.

Best regards
Frank

Responding to this forum post for completeness- I already sent the test build via email.

It is a known issue and is fixed internally. We don’t have an exact date for release of 3.5.18 but I would guess 1-2 weeks.

Julie

You might find these links to be helpful:
https://docs.wisej.com/docs/getting-started-1/license-activation
https://docs.wisej.com/deployment/troubleshooting/license-activation

The Wisej Server Express License has a minimum version of 3.5.6.9. So my guess is that’s why it’s not working- you are using an older version of Wisej. Using a Standard Server License should fix the issue.

The error is probably something to do with your production environment not being able to load the content from the CDN. TinyMCE is a commercial product, and because of that we are required to use their CDN to use the packages, not like ChartJS or anything else that we can distribute. Unfortunately,  it’s not possible for us to track it unless we get some sort of an error.

Regarding the try-catch block, unfortunately you won’t be able to do that in your code- it would be a modification in either qooxdoo or the client side of Wisej.

Julie

Hello,

Can you please attach a a screenshot of the DevTools console?

TIA,
Alaa

Hi Wilfred,

IIS Express doesn’t support ASP.NET Core. ASP.NET core uses kestrel and is self hosted.

IIS on the other hand has the ASP.NET Core Bridge Handler which is native (not managed).

Also, Authentication by IIS is not handled by Wisej.NET, and unfortunately it’s out of scope for the free tier support that this forum offers!

If you’d like additional support, you can order a professional support package.

For more info, please visit our Services section on our website.

Best Regards,
Alaa

OK, so actually using the IIS Express profile when starting the page in the debugger.

Uncommenting this line in web.config:

Snippet

<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />

And uncommenting and changing to this:

        <aspNetCore stdoutLogEnabled="false" hostingModel="InProcess" processPath="bin\Debug\net9.0\MGRegnskapWisej.exe" arguments="" />

In startup.cs I added this:

Snippet

app.MapGet("/whoami", (Microsoft.AspNetCore.Http.HttpContext ctx) =>
     ctx.User.Identity?.Name ?? "unauthenticated")
   .RequireAuthorization();

And I can confirm that when browsing to /whoami it is working.

But when I browse to http://localhost:54429/ I get a blank page. And no code in Program.cs is executed.

So the question is can it work in IIS Express and what am I missing now?

I have uppdated the launchSettings.json for the IISExpress profile:

The project’s properties enable Windows Authentication and disable Anonymous Authentication. Open the launch profiles dialog:

1. In Solution Explorer, right click the project and select Properties.
2. Select the Debug > General tab and select Open debug launch profiles UI.
3. Clear the checkbox for Enable Anonymous Authentication.
4. Select the checkbox for Enable Windows Authentication.

Snippet

{
  "profiles": {
    "MGRegnskapWisejWebDesktopApplication": {
      "commandName": "Project",
      "launchBrowser": true,
      "environmentVariables": {
        "WEBSITE_PATH": "$(MSBuildProjectDirectory)"
      },
      "applicationUrl": "http://localhost:5000"
    },
    "WSL": {
      "commandName": "WSL2",
      "launchBrowser": true,
      "launchUrl": "http://localhost:5000",
      "environmentVariables": {
        "ASPNETCORE_URLS": "http://localhost:5000",
        "WEBSITE_PATH": "$(MSBuildProjectDirectory)"
      },
      "distributionName": ""
    }
  },
  "iisSettings": {
    "windowsAuthentication": true,
    "anonymousAuthentication": false,
    "iisExpress": {
      "applicationUrl": "http://localhost:54429",
      "sslPort": 0
    }
  }
}

But it is still not working.