All Answers

Hi Rui,

a lot of small issues to stabilize until the product becomes mature and stable to be used in real live applications (I remember that this evolutionary process have been  long and painful with VWG, and when finally start being usable the company closes).

I agree 100%. The first usable version of VWG was version 7 and soon after they went free and closed the door.

Why I’m not too worried about Wisej maturity? While VWG did everything from the ground up, Wisej is built on top of solid components.

VWG took a very long road of recreating System.Windows.Forms namespace. This is a very hard job that requires an enormous amount of effort. It needs a large team or a long time. Note the Mono version of Windows Forms isn’t as mature as VWG.

Wisej took a different path. Wisej extends System.Windows.Forms, meaning some basic features are already there, namely DataBinding.

WVG did their own Javascript components. Wisej uses Qooxdoo and extends the widgets only when needed.

As you can see, the amount of work needed to get the product stable is quite different.

WVG lost momentum because of the enormous time it took to release a stable product. Gizmox lost a lot of customers while it was stabilizing the product.

As I understand, Wisej prefers to release a stable product with missing features. The included features are stable: you can use them and trust they do whatever they are supposed to do. Later releases will be feature complete. As I said, I don’t expect Wisej to take too long to release a feature complete product.

This strategy is important as it’s quite difficult to write a migration application, because we don’t know exactly what are the properties that Wisej implements and the ones it doesn’t. Anyway the end result of the application will be a designer file that builds. Most of the time it won’t need further changes, but sometimes it will need fixes.

One of the biggest WinForms to VWG migration issues was the asynchronous MessageBox. (I’m facing this problem again on Xamarin/Android). The problem was solved on VWG 7. Wisej doesn’t have this problem so migration from WinForms should be a lot easier.

No sample needed, it’s very simple.

System.Windows.Forms.Control.MouseButton : Gets a value indicating which of the mouse buttons is in a pressed state.

see also https://msdn.microsoft.com/de-de/library/system.windows.forms.control.mousebuttons(v=vs.110).aspx

Your Wisej.Web.Control.MouseButton save the last button, once you click, the value remains permanent.

The value must be chaged to MouseButtons.None, when the mouse button is released.

Greetings

Hi Tiago

sorry i didn’t see that. That sounds very good. And with vwg, does wisej provide anything for migrating vwg applications to wisej?

I am an old VWG user and I am seeing a long and painful migration process from VWG. Mainly because a product as recent as the Wisej, must have a lot of small issues to stabilize until the product becomes mature and stable to be used in real live applications (I remember that this evolutionary process have been  long and painful with VWG, and when finally start being usable the company closes).

No seriousness by the Gizmox the way they close the door and left all users/developers orphan (paying users). The only serious way in a situation like this is to make all code available for the users. But ok, this is another story and I am crossing fingers that with Wisej will be different.

Thanks & regards,

Rui

How to activate server license? Is just by write it in web.config?

The step by step from VWG to Wisej will be great. Namely, a list of unsupported controls entirely or partially.

I am an old VWG user and I am seeing a long and painful migration process from VWG. Mainly because a product as recent as the Wisej, must have a lot of small issues to stabilize until the product becomes mature and stable to be used in real live applications (I remember that this evolutionary process have been  long and painful with VWG, and when finally start being usable the company closes).

No seriousness by the Gizmox the way they close the door and left all users/developers orphan. The only serious way in a situation like this is to make all code available for the users. But ok, this is another story and I am crossing fingers that with Wisej will be different.

Thanks & regards,

Rui

Great! I already activate the developer license the Wisej icon.

But I still having the same problem when publish the Hello World project to the IIS, the same popup message saying “Beta Server License Expires on: 01-11-2016”. I changed the “Wisej.LicenseKey” in web.config with my Web Developer License key, but without any success.

Thanks & regards,

Rui

Hi,

I guess you already have a non beta licence, meaning a trial license or a developer license.

In order to activate it, open a Wisej project, open the designer view of a page or form and click on the Wisej icon at the bottom right corner of the designer.

A popup whill show where you can enter and activate your new license key.

Hi same here – I’ve downloaded the 1.3.0 build but never get prompted for a license key. Is there some other step required when coming from the beta?

Thanks

Nic

Hi Rui,

There are some issues with the vanishing icons and duplicating icons. Those aren’t Wisej issues (Telerik users also complain about them) but rather VS issues.

Have a look at VS2015 toolbox – Wisej icons issue thread.

Hi David,

I have a lot of background threads in my application and it took quite a long time for me to work out how to get it all going (with the help of Luca). Basically the “magic” is to wrap any updates on any wisej control on the background thread in an Application.update task – as I understand it this ensures that the wisej framework will then push these updates to the browser assuming you are running in websocket mode (which you won’t be if you are using VS on windows 7).

i.e.

Application.Update(this, () =>

{

//Do something that updates my UI

}

Note: this in my snippet above is any wisej control.

For non-web socket connections you also need to have a wisej.timer on the form attached to an event on the server, even if that event is empty, to ensure that wisej processes your other updates.

HTH

Nic

Hi Rui,

after “reset toolbox” as suggested by Tiago, you can “Choose Items” and
browse to “Wisej.web.dll”.

We will also check our installer to track down the problem.
Please also keep in mind to close all Visual Studio installations during the installation.

Hope that helps.

Best regards
Frank

I did the reset toobox and just disapear all Wisej Controls group in Toobox. I just have tried to remove Wisej installation and reinstall it but don’t appear the Wisej Controls group anymore.

Hi Rui,

We will soon publish a simple guide with the basic steps and what to check for: WinForms to Wisej and VWG to Wisej.

There is also a tool that we mentioned in another answer. It is developed and used by fecher LLC  (our service partner and sister company) and it’s used on migration projects – it’s not meant for redistribution at the moment.

If you are interested in their services, I can bring you in contact.

Best regards
Frank

Hi Rui,

Please try to “Reset Toolbox”as it should solve the issue.

Frank, Big thank you for the quick answer!

Will try.

Hi Stanislaw,

thanks for your interest in Wisej. One of it´s biggest strength is to be able to integrate external components quite easily.

Please take a look at the ChartJS example in our download section.

We will come up with more samples soon.

Hope that helps.

Best regards
Frank

Hi Ralf,

sorry for the delay in answering.

Would it be possible for you to wrap up a small sample that shows the problem ?

Thanks in advance !

Best regards
Frank