All Answers

Hello Alaa,

All I can say is that I did what I explained in my question and have that prompt. I simply installed your Nuget packages in a new project and have the prompt. I uploaded a Screenshot which should have all necessary info. You can also see that the chart works without me installing anything, but the Application.Eval throws a JS error that ej is not defined.

Afterwards I installed Syncfusion Essential Studio 20.2.0.36. I need the JS package, right? It changes nothing for now. Why do I need to install and implement anything just to register the license? And how exactly do I do that in a WiseJ project now?

Greetings

edit: also I added the rest of my test code; I’m aware the register License is at the wrong spot, but the ej JS namespace is not existent anyway.

It is not working, because my wiseJ Toolbar is not apper the deactivate, when i open a wiseJ project in my machine. I have other option?

Hi Jadson,

if you open the Visual Studio click on the License Information tool in the bottom right of the Wisej Toolbar.
It shows an option “Deactivate License”. After this you can re-register with your new license.

Best regards
Frank

Hi Sascha,

To add to my previous answer, there is no commercial validation with the default version included in our Widget (it’s from CDN), but now Syncfusion requires this so you must use the registerLicense method in JavaScript.

You can add this peace of code below into your application’s main entry point,
Application.Eval("ej.base.registerLicense('someLicenseKey')")

This should also do the trick!

Also, as stated here: Introducing License Key Validation For The Essential Js 2 Platforms, you would only need to use ej.base.registerLicense with Essential Studio 2022 Volume 1 or greater.

Our extension uses an old CDN package, so in theory, you shouldn’t have that prompt!

HTH,
Alaa

Hi Sascha,

You’re probably missing the Syncfusion assemblies, the “Syncfusion” namespace is part of those!
Make sure that you have Syncfusion installed on your machine, and then you can use any of the methods described in their documentation: Syncfusion |How To Register In An Application

This is how you’ll be able to register your license!

HTH,
Alaa

That’s what I’m trying. Scrollbars=none and I can get the mouse wheel events. And I can zoom my picture (and that’s working either). What I can’t do is that: I have the panel and some controls that are (partially) outside the boundary. I want programmatically to “move the scrollbars” of the panel. In Winforms I’m getting this by setting  Panel1.AutoScrollPosition. Here it’s not working.

Hi
Sadly you can´t control the scrolling from the server
Mouse wheel is already supported

Maybe as workaround you can set scrollbar=Hidden and
use the mouse wheel to scrollbar the panel

Regards

Hi Adrian,

If you want to use Wisej for rotation, we have an extender https://docs.wisej.com/docs/controls/extenders/rotation for that:

– For Rotation : this.rotation1.GetRotation(this.pictureBox1).RotateZ += 20;

-For Scale (Zoom) : this.rotation1.GetRotation(this.pictureBox1).ScaleX += 20;this.rotation1.GetRotation(this.pictureBox1).ScaleY += 20; this.rotation1.GetRotation(this.pictureBox1).ScaleZ += 20;

If you want to apply effect directly on Bitmap, Check this link for more details https://docs.microsoft.com/en-us/dotnet/api/system.drawing.image.rotateflip?view=dotnet-plat-ext-6.0

Happy Coding,

Kevin(ITG)

Hi Andrew,

do you have a URL where we can try that? Or could you wrap up the code in a test case?
You can either post here or send it to supportATwisej.com if it contains private information.

Did you have a chance to test with an IOS device?

Best regards
Frank

Hi Adrian,

Can you send us a sample code?

Best,

Kevin(ITG)

Hi Tiziano,

The issue is that you’ll have to specify the target framework and runtime for the “dotnet publish” command!

The fix would be the following:

dotnet publish -f “MyProject.csproj” -c Release -o /app/publish —framework net6.0 —runtime linux-x64 

You don’t have to fiddle with the .csproj files, it’s not a Wisej.NET issue!

You can take a look at all the Target Frameworks Identifiers here: https://docs.microsoft.com/en-us/dotnet/standard/frameworks

And the Runtime Identifiers from here: https://docs.microsoft.com/en-us/dotnet/core/rid-catalog

From there you can containerize your app and use it in GitLab!

HTH,

Alaa

We removed the change because it created more problems. We tried the nested CSLA data source directly with WPF and it doesn’t work there either.

IBindingList is part of System.ComponentModel (used by winforms) and it’s more flexible that INotifyCollectionChanged (part of System.Collections.Specialized, and used by WPF with a lot of limitations). Neither of those is specific to Winforms or WPF. Wisej.NET  now supports both. The problem with your sample is using child BindingSource bound to another child BindingSource and then to another that returns a list from another source CSLA (outside of our control) that mixes things. If we try directly with BindingList<> and ObservableCollection<> it works fine. Our DataGridView (not winforms) is an order of magnitude more integrated with server features and data binding than any other web grid.

We also tried Csla.ApplicationContext.PropertyChangedMode = Csla.ApplicationContext.PropertyChangedModes.Xaml and it seems to work also with child of child, etc. Except it still doesn’t work correctly with plain WPF but it’s not our concerm.

Hi,

I updated to 3.1.1. Looks like the change is gone?

Anyhow, I would rather be using the WPF databinding model. It’s a more modern/better way of doing databinding compared to the ancient WinForms model.

You can instruct CSLA to do this with this code (It is default value so it is actually not needed):

Csla.ApplicationContext.PropertyChangedMode = Csla.ApplicationContext.PropertyChangedModes.Xaml;

And that seems to be working very fine. No problem when adding or deleting rows.

But there is one problem and the reason why I’m using the Windows forms mode. Csla.ApplicationContext.PropertyChangedModes.Windows
Look in this thread:
https://wisej.com/support/question/datagridview-focus-jumps-to-the-first-column-after-editing-a-cell
I think it is the sole reason why I’m using Csla.ApplicationContext.PropertyChangedModes.Windows

I have provided a new sample code. This time it also contains a WinForms project for reference. The WinForms project has all sorts of problems, including the old WinForms DataGridView that no one should be using anymore. But I hope that Wisej is striving to be a better Choice. Not mimicking all problems in WinForms. I use the grid from DevExpress and it handles the problems.

I have also discovered another problem. When you delete all sons. When the last Son i deleted the cildren do not go away. This is also a problem when using Xaml (WPF) mode.
Best regards,
Wilfred

I’m sorry but same problem with 3,0.17.