All Answers

For those of you who downloaded 1.2.53 and are facing problems with Application.Update,
please upgrade to version 1.2.54 (just uploaded). Thanks !

A new build (1.2.53) has just been uploaded. It includes the following fixes/enhancements:

I want to the same sample 🙂

Hi,

The original problem I reported was with version 1.2.45. After updating to 1.2.51 I don’t see the error anymore, but the ComboBox behaviour/binding is still not the expected.

But I’m writing to point out a more general problem: with the fast pace you update the builds, which is excellent by the way,  we (at least I) cannot keep track of what’s going on. For example, I saw that there was a new version in the Beta Updates post, version 1.2.49 and thought to myself, ok, let’s try it to see if the problem was fixed. And when I updated I got 1.2.51, where the problem was partially fixed. But since 1.2.51 is not reported in Beta Updates, I have no clue whether it was created before or after I had seen the problem with version 1.2.45. And the time reporting of the posts (16 hours ago, 2 days ago etc.) is not very useful. So what I think would be very useful is:

1. if possible have the exact time of a post/answer in the forum so that we can compare — I understand that this can be done only if available in the forum software…
2.  you drop a line in the Beta updates whenever a new build is uploaded (even without any explanation/comment) just to let us know the time the build was published — hope this is not too much overhead for you…

Hope I’m not becoming a PITA !

Best,
Alex

Great! Thank you.

Best,

Corvin

Quick answer: Yes.

var httpAuthCookie = new Cookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(authTicket)) {Path = FormsAuthentication.FormsCookiePath};

Application.Cookies.Add(httpAuthCookie);

Best,

Corvin

Hi Luca,

No embarrassment necessary. You guys (particularly yourself and Frank – those that hang out on this forum) are doing an amazing job on both WiseJ and keeping us (your beta users) in the loop. I’m totally aware that this is a beta and I’m grateful to you for involving us and being so responsive to the issues we find. It gives me a great deal of confidence in the future of the WiseJ.

Nic

Thanks, quick question: are you using Application.Cookies?

Hi Corvin,

Thank you for the sample. There are issues with the sample and with the dynamic layout vertical auto resizing in Wisej. I will send you the fixed TestflowLayoutPanel and a second sample implementing the image in the drawing – after the issues that your sample uncovered are fixed.

Best,

Luca

Ah, thank you!

Have attached a Screenshot of the Nullreference-Exception.

Best,

Corvin

Hi Nic,

My apologies for not testing this. We were rushing to update a show stopper in .48. It’s fixed now. Also Application.Download(file) automatically root the file (if unrooted) to the application’s directory.

And, to make this look less embarrassing, we are  building a set of regression tests also incorporating all the feedback we get here and it will be a requirement on the release build.

Thank you again,

Luca

Hi Corvin,

For the toolbox issue, please refer to Tiago’s answer. It’s a common VS issue when installing toolbox items. Usually right-click -> “Reset Toolbox” works.

I had the toolbox stuck as well, but it’s not caused by Wisej, it happened for me without Wisej. It was more frequent when using the search textbox at the top of the toolbox to filter the tools. After updating to VS2013 Update 5 and VS2015 Update 2 I haven’t been able to reproduce this problem and other Visual Studio issues.

ClientSize, Size, and all structure properties can only be assigned. You cannot change the value of a structure returned as a property.

The ControlCreated event was hidden on purpose since it was a new “structural” event that should be handled with care. I have logged an enhancement to make it visible in the editor at least. Now it’s set to Browsable false and EditorBrowsable never.

The SplitterDistance has a new bug, fixed in dev not updated yet. It was caused by a fix to a design time issue with the SplitContainer not updating the rendering when resized in design mode.

For the NullReference exception, can you please add “debug”:true in your json config. It will show the stack trace when popping the message box (if it’s coming from the server).

Let me know.

Best,

Luca

Right.

Now we are trying to understand why the application doesn’t run.

Hi Corvin,

About the toolbox icon multiplication issue, please refer to VS2015 toolbox – Wisej icons issue. It happened to me 3 times on VS2015.

To update this thread:

• The .lic files (developer and server) are generated into \ProgramData\IceTeaGroup\Wisej.
• For the server license, the same .lic file is (should be) duplicated in the application root to simplify deployment.
• When deployed, the server app will run with or without the license and also without a connection to the internet.
• The wisej-server.lic file can (not necessary if the server can access the internet) be deployed with the app.

Will add a troubleshooting page to the docs.

Updated to 1.2.49.0 but no improvements on the LIC file generation front.