All Answers

Yes, my bad. It was like that but it was changed. Now the new set of arguments is updated instead of reloading a new session. This lets your code process different arguments in the URL without recreating the session. Changing the URL causes a reload anyway. You can get notified of a refresh or change of arguments by attaching to:

Application.ApplicationRefresh += ...

The arguments in the URL are available using this collection:

Application.QueryString

If you use “sid” and “cookieless” is false when you hit refresh Wisej will always start a new session since sid is invalid. In fact that is a “trick” to use when debugging to force the start of a new session. I add “?sid=new”.

Hi Luca,

I’ve tested the ways you explained,

“cookieless sessions” option runs very well as you explained.

On the other hand, may the first option run a bit different? If I use url argument name “sid” with any value (sid=1, sid=anyvalue) it’s ok, every tab starts a new context/session  from the beginning as the first option. But if I use random argument name and value (abc=1, xyz=anyvalue),  new tabs starts with previous tab’s state.

Serkan,

Hear, hear

A new build is available (1.2.10). It includes the following fix and enhancement.
Please note the namespace change !

I contacted you directly.

Hi Luca,

It would be good to solve it, so what is the webex session?

Alex

Hi Alex,

I tried with up to two nested UserControl containers added to your test but cannot reproduce.

UserControl uc = new UserControl() {
    Size = new Size(300, 300),
    BorderStyle = BorderStyle.Solid
 };
 UserControl uc2 = new UserControl()
 {
    Size = new Size(300, 300),
    BorderStyle = BorderStyle.Solid
 };
 uc.Controls.Add(tabPages);
 uc2.Controls.Add(uc);
 sc.Panel2.Controls.Add(uc2);

I also tried to put the tabtxtID in a UserControl in a tab page in a TabControl in a UC in another UC in the SplitPanel in the SplitContainer… 🙂

The initial state is correct, only toplevel containers start with Visible=false. When they transition to visible the first time you get the creation, OnLoad, etc. If you create a standalone non-toplevel control it’s created when you call Show() or when it is added to a visible or created container.

Make sure that the Wisej.Web assembly is updated and that the project is not using a cache previous build. I’m also available to setup a remote webex session, if you are available please let me know directly.

Best,

Luca

Hi Alex,

I tried with up to two nested UserControl containers added to your test but cannot reproduce.

UserControl uc = new UserControl() {
    Size = new Size(300, 300),
    BorderStyle = BorderStyle.Solid
 };
 UserControl uc2 = new UserControl()
 {
    Size = new Size(300, 300),
    BorderStyle = BorderStyle.Solid
 };
 uc.Controls.Add(tabPages);
 uc2.Controls.Add(uc);
 sc.Panel2.Controls.Add(uc2);

I also tried to put the tabtxtID in a UserControl in a tab page in a TabControl in a UC in another UC in the SplitPanel in the SplitContainer… 🙂

The initial state is correct, only toplevel containers start with Visible=false. When they transition to visible the first time you get the creation, OnLoad, etc. If you create a standalone non-toplevel control it’s created when you call Show() or when it is added to a visible or created container.

Make sure that the Wisej.Web assembly is updated and that the project is not using a cache previous build. I’m also available to setup a remote webex session, if you are available please let me know directly.

Best,

Luca

Hi guys,

Well, unfortunately the problem is exactly as it was in my main project! 🙁 The toy project I sent you works indeed, but not my main project.

Since there I have a more complex structure of containers, all contained in a top Page, search whether this wrong initial state you discovered is correctly transferred to other container objects. I would suggest the UserControl, since I wrap my components in UserControls.

Sorry for that,
Alex

The templates need to be updated for sure. Good catch!

The reason for Wisej.Data is what you wrote. The data binding is shared between Wisej.Web and Wisej.Mobile.

Best

Luca

Hi,

All 3 issues are fixed. Thanks.

There is plenty of documentation today:

• Concepts from Configuration to Designer
• Namespaces – I guess most of it is available now

Tiago,

for your convenience I have attached your latest sample with the namespace changes.

For components you can use either System.ComponentModel.Component or Wisej.Web.Component.

In your case it’s better to use System.ComponentModel.Component since it only lives on the server side.
Wisej.Web.Component works the same but are also registered with the ComponentManager which manages the server/client components.

Hope that helps.

Best regards
Frank

No you always need it or it won’t compile.