Thanks for answers
Basically I fixed the issue by manually adding controls to toolbox from NET assemblies in WiseJ namespace.
Thank you for the info. I was using 2 webs with Applications withing those webs.
It turned out that I had a newtonsoft.json.dll that was the wrong version in one of them and that caused my problem.
I am still getting the “Invalid session happening being caught by the Wisej.onException javascript error handler but the session doesn’t actually seem to be invalid because the app is still working… So I am not sure what is going on.
Consider this closed.
Thanks.
Shawn
We have added an option to poll the server at a configurable interval automatically when a WebSocket connection is not established and the application needs to update the client in a background task. It’s basically a WebSocket emulation without using long polling which blocks a thread.
You can run as many wisej apps as the server will take. I don’t understand if the setup is done nesting applications. Or is it two different domains using the same server and applications with the same application name? Added a second site to the same IIS?
You can also add this to <head> in your Default.html:
<meta http-equiv=”X-UA-Compatible” content=”IE=11″ />
You can also add this to <head> in your Default.html:
<meta http-equiv=”X-UA-Compatible” content=”IE=11″ />
Hi Bogdan,
After installing VS2017 15.6.2 I created a new project without issues. So this isn’t related to this specific version of VS2017.
To check the Wisej version, please have a look at the attached picture.
Hi Bogdan,
I’m running VS2017 15.6.1 and it also happened to me.
VS solved it when I double clicked on the project Properties icon. After that, I created new projects without problems, even after closing VS.
You can try a number of things a bit more reasonable then double clicking here and there:
Thanks Luca,
This post from Felix Chan (https://wisej.com/support/question/application-downloadpath-name-result-in-redirected-to-download-wx-and-404-error) really helped me figure it out once you had given me the clue.
Nic
You can implement the Wisej.Core.IWisejHandler interface and turn any control into a response handler. Then set the URL to this.GetPostbackURL() where “this” is the control implementing Wisej.Core.IWisejHandler, could be a subclass of Wisej.Web.Video.
You’ll get a callback from the client when it tries to download the video to ProcessRequest(HttpContext) which is the same as an ASPNET service. There you can send the stream back to context.Response. You have full control of the response data, content type, etc. This is how the PdfViewer uses the stream option.
You need to hold on the stream and release the memory when not needed. Also, note that the HTML5 video tag doesn’t support live video streaming. The stream that you send to the response will be fully downloaded by the browser.
HTH
Hi Cristian,
Thank you for the sample. We could trace the issue and although it doesn’t happen on Form, it does happen on Page objects.
The issue was logged with id WJ-8798
As a final note, Vista-2 is not a theme distributed with Wisej. It’s a custom made theme and it should be maintained by its authors.
Hi,
to be sure to exclude the problem of old themes, I used the Vista-2 theme that I downloaded and that is not in the default themes.
I uploaded a minimized project to verify the problem
please, can you check it?
thank you
Regards
Cristian
Somehow we didn’t get the email from the online form. I’ll make sure you receive the answer.
We can’t reproduce. We could only reproduce when using the old theme with the double left border when the textbox gets the focus and only on FireFox.
ARGH!
solved, closing the Visual Studio and reopen the project
regards
Cristian Zerbinati
Hi Matteo,
you might want to try to exclude the directory of your Wisej app from the Compatibility View list.
Find some information here:
Best regards
Frank
I have a problem, a customer must necessarily use the site in compatibility mode
with this configuration i have this error:
Sorry,this browser is not supported.
can you help me please?
Hi Andrew,
When you set
e.Handled = true;
in the SessionTimeout handler, you can close the browser whenever you want. The application will stay alive and “in memory” until it expires. As the Session Expiration section states:
An “abandoned” session expires after twice the sessionTimeout value (in seconds) specified in Default.json or the default 120 second value.
(…)
All the windows (pages, forms, …) in the application are closed and disposed. (…) All the child controls are also disposed firing the Disposed event.
In the attached sample, I also use the Form.Closed event and the Page.Disposed event to detected session expiration and application close/unload.
But the appropriate event is the Application.ApplicationExit.
Please have a look at the attached SampleSessionTimeout sample. The file LogFile.txt will store all the information you need. If I may suggest some steps:
Please notice the MainPage Disposed message shows after the ApplicationExit message.
I think Application.ApplicationExit event answers your requirements.
Hi Rudy,
On the administrator image there was an extra <style type=”text/css”> .st0{fill:#505050;}</style> declaration.
Once removed, you can fill it with whichever colour you want.
The project with the fixed mixin and all step-by-step files is attached.
