You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been doing exactly that. It's been pretty simple. I've removed all references to VWG and replaced them with the references to WiseJ. I've also had to go and undo all the non-modal closing form code I as WiseJ works just like Winforms but other than that it has been a very straight forward process.
The bonus has been that WiseJ apps seem much more stable than VWG (i.e no cache clearing to get rid of issues).
Basically the process is exactly what Nic described:
Namespace change
Workaround removal
Obsolete/non-functional properties removal
Take advantage of new features
The modal workflow is a great feature (VWG had it too, by the way, but it had to be enabled in web.config). We also have the async approach. The Show (for MessageBox as well) and ShowDialog methods have an optional onclose parameter that is called asynchronously and a modal optional argument that disables the modal workflow. It's an Action, so you can use it like this:
form.Show(onclose: (result) => {
});
// ShowDialog is always modal, but the onclose callback works as well.
form.ShowDialog(onclose: (result) => {
});
And you can make a non-modal form show the modal mask on the client and act as a modal dialog but completely asynchronous:
form.ShowModalMask = true;
form.Show(onclose: (result) => {
});
result is DialogResult.
One additional tip about testing. Sometimes when testing you may need to start a new session to force the re-creation of the controls and Load events. Instead of closing the browser you can simply add ?sid=new or ?sid={anything} and Wisej will interpret it as an invalid session and will create a new one.
I must confess I didn't try to convert a VWG project to Wisej since all my projects depend on MvvmFx. Wisej isn't stable enough to port this library to Wisej so I must wait.
Anyway, I guess you also have to remove the ProjectTypeGuids on the project file.
It's been some time since the question was answered. In the meantime, Wisej has advanced and is used in production by a number of organizations worldwide to realize impressive line of business applications. Visual WebGUI code can be easily ported to Wisej and will benefit from its advantages on stability, performance, and extensions.
In order to get started, take a look at the following resources:
Activity
itg-assistant commentedon Jun 12, 2026
Nic Adams answered 2016-05-26 07:00:09 UTC
Morning Ewan,
I've been doing exactly that. It's been pretty simple. I've removed all references to VWG and replaced them with the references to WiseJ. I've also had to go and undo all the non-modal closing form code I as WiseJ works just like Winforms but other than that it has been a very straight forward process.
The bonus has been that WiseJ apps seem much more stable than VWG (i.e no cache clearing to get rid of issues).
HTH
Nic
itg-assistant commentedon Jun 12, 2026
Luca answered 2016-05-26 14:00:14 UTC
Thanks Nic!
Basically the process is exactly what Nic described:
Namespace change
Workaround removal
Obsolete/non-functional properties removal
Take advantage of new features
The modal workflow is a great feature (VWG had it too, by the way, but it had to be enabled in web.config). We also have the async approach. The Show (for MessageBox as well) and ShowDialog methods have an optional onclose parameter that is called asynchronously and a modal optional argument that disables the modal workflow. It's an Action, so you can use it like this:
form.Show(onclose: (result) => {
});
// ShowDialog is always modal, but the onclose callback works as well.
form.ShowDialog(onclose: (result) => {
});
And you can make a non-modal form show the modal mask on the client and act as a modal dialog but completely asynchronous:
form.ShowModalMask = true;
form.Show(onclose: (result) => {
});
result is DialogResult.
One additional tip about testing. Sometimes when testing you may need to start a new session to force the re-creation of the controls and Load events. Instead of closing the browser you can simply add ?sid=new or ?sid={anything} and Wisej will interpret it as an invalid session and will create a new one.
Best,
Luca
itg-assistant commentedon Jun 12, 2026
Tiago Freitas Leal answered 2016-05-26 15:20:47 UTC
I must confess I didn't try to convert a VWG project to Wisej since all my projects depend on MvvmFx. Wisej isn't stable enough to port this library to Wisej so I must wait.
Anyway, I guess you also have to remove the ProjectTypeGuids on the project file.
itg-assistant commentedon Jun 12, 2026
Thomas (ITG) answered 2017-11-12 07:02:23 UTC
It's been some time since the question was answered. In the meantime, Wisej has advanced and is used in production by a number of organizations worldwide to realize impressive line of business applications. Visual WebGUI code can be easily ported to Wisej and will benefit from its advantages on stability, performance, and extensions.
In order to get started, take a look at the following resources:
Wisej Homepage
Wisej Documentation
Wisej Blog
Visual WebGUI migration guidelines