All Answers

You have to remove all your references to System.Drawing.Common as indicated in the documentation.

The sample code you posted compiles without issues omce you remove the external Datagraph.Ext.Font library which is using System.Drawing.Common (which is based on GDI+ and dropped on Linux by Microsoft). That library is not available on NuGet but my guess is that it’s bringing in the System.Drawing.Common package. You can modify the NuSpec and exclude the asset (see NuSpec documentation).

Hi Frank,

finally, after some experimenting with several test projects, I could pinpoint the cause of the issue to the following:
What I did before the issue came up was, to switch the projects configuration (first the test project and then the “real” one) to enabling Windows Forms and setting the target framework to net8.0-windows; reason for this was that we need to use a reporting library from ComponentOne because the existing code of the application we are porting wo Wisej relies heavily on this library. As the lib is for Windows Forms, this switch was necessary according to their support. (Of course, we only use it for generating PDFs, no WinForms UI 😉  )

Obviously, by this switching of the output type, something got messed up in the .vbproj file; I repeated the steps in a fresh Wisej test application, compared the .vbproj files and adapted accordingly. After this and cleaning up the \bin and \obj folders, the designer works again!

Thanks and best regards, Robert

It seems to be impossible having the correct reference to Font and other System.Drawing object.

You should rename System.Drawing namespace inside System.Drawing.Managed to avoid this behaviour.

hi,

I have reproduced the issue in a small project because the real one is too complex to explain, but the issue is the same.

many thanks,

Luca

Hi Robert,

did you already check our advices in the troubleshooting section here?

https://docs.wisej.com/docs/getting-started-1/troubleshooting#designer-error

Can you please attach your test application so we can take a closer look?

Thanks in advance,
Frank

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