All Answers

Hi Tiziano,

It’s not something related to your code, but it happens only when the app is running in net9.0-windows.

If you run it in net9.0, it should work just fine.

We’ll continue to investigate the issue on our end and let you know!

Best Regards,
Alaa

Hi Luca,

thanks for your answer.

We need that library, anyway we could rewrite all the library code.

But, supposing to remove all System.Drwaing references, like I did in the screenshot and the attached code, what should we use instead of System.Drawing?

Many Thanks,

Luca

Hi Edmond,

Audio is played through browser media support. It’s beyond Wisej.NET support scope to tell if it supports to HIPPA rules or not.
Check out audio formats etc. here

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/audio

Best regards
Frank

Hi Edmond,

Wisej 3 only supports Visual Studio 2019 and 2022, Wisej 4 only 2022.
You may have some luck trying older versions but they are no longer supported.

Best regards
Frank

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