Hi Felix,
WJ-8159 is fixed in release 1.3.47.
Best regards
Frank
Hi Andrew,
InputType has been added (WJ-8153) in Wisej release 1.3.47
Best regards
Frank
Hi Andrew,
WJ-8166 is fixed in the latest Wisej release (1.3.47).
Best regards
Frank
Hi Felix,
WJ-8158 is implemented in the latest Wisej release (1.3.47).
Best regards
Frank
Hi Adil,
WJ-8175 is fixed in the latest release (1.3.47).
Best regards
Frank
Check the Application Pool, it must be Integrated or it doesn’t process the handlers.
Also, sub applications in IIS inherit the parent’s web.config. The main app config may have a setting that prevents IIS from processing requests to pages that don’t actually psychically exist. Try to access the child Wisej application by adding Default.html to the URL.
It’s the <module> setting in wisej’s Web.config that recognizes url without the extension (pretty url) and matches them to a .json config which in turn redirects to the html specified in the json. If IIS is configured to check the existence of the URL it will fail since it thinks that the url without a file is a directory.
Wisej defines all its visual properties in the single theme files: https://wisej.com/docs/html/Themes.htm
Colors, fonts and images are all indirected to simplify the management of the themes and the handling of the data. For example, instead of setting an image or a color or a font by value, you simply set it by the name defined in the theme. The built in themes define 4 fonts: “default”, “window-title”, “defaultBold”, and “menu”. You can modify one of these, or add new fonts. Then in your app you assign the font using the name in the theme, this way when a theme changes everything is updated automatically.
The font definition in the theme has many options, fortunately they are all handled visually using the theme builder. You can define only few properties or define multiple families and multiple sources.
The json definition below changes the “default” font family to “roboto”, “arial”. I have also attached the actual mixin file. You can add it to /Themes to override any theme loaded by the app.
“fonts”: {
“default”: {
“size”: 13,
“family”: [ “roboto”, “arial” ],
“sources”: [
{
“family”: “roboto”,
“source”: [ “https://fonts.gstatic.com/s/roboto/v15/CWB0XYA8bzo0kSThX0UTuA.woff2” ]
}
]
}
}
Best,
Luca
Hi Andi,
I tried the Window1 -> Window2 with the panels docked in Window1 and it seems to work well. I suspect the issues you are seeing are related to the designer in visual studio. For the size problem at runtime would it be possible for you to send a small test case?
About the designer: we use the standard Visual Studio WinForms designer and all the behavior you see is the way it works with the WinForms designer (and WPF). When you delete a component from a base class Visual Studio cannot delete all the references to the deleted component in the derived classes. In general, when you update anything in a base class, the changes do not override the derived classes. The only change that sometimes Visual Studio can propagate is the name of the component.
HTH
Best,
Luca
Hi Andrew,
I think it’s possible. Web.config shouldn’t be a problem since wisej’s settings are very limited, just 2, the module and the handler. If Wisej is the main app “hosting” vwg in iframe panels you could also retain the vwg session across iframes using vwg vwgcontext (I don’t remember exactly the argument name in the url).
From the Wisej hosting app you cannot access the vwg session since it would be in an iframe. You can pass arguments through the url. From the “child” vwg app you may be able to access the Wisej session and all the wisej objects. I’d have to try. There is a static method in Application:
Application.RestoreSession(HttpContext)
or
Application.RunInContext(HttpContext, Action);
It lets you reload a Wisej session from the System.Web.HttpContext which should be accessible from vwg.
Let me know if this is what you need.
Also, if there are some missing features or controls that are critical for the migration let us know.
Last but not least, the http://fecher.net (and http://fecher.eu) developers are very experienced in migrating vwg to wisej and are developing tools and methods that may be useful. But of course, they have a cost.
Best,
Luca
You can using javascript. We don’t pass the local storage back to the server since it could be quite large. You can execute any js method directly using Application.Eval().
My suggestion is to add your javascript functions in .js file(s) part of your project and use the methods from the app. You can create either global js functions or create a js object with your functions, like a namespace. Your javascript code can also call back your application on the server using [WebMethod], including methods in Program.cs or on a top level page or window.
I noticed that Application doesn’t have the Call method to be able to automatically serialize parameters, will add.
Hi Adil,
thanks, I could reproduce and logged WJ-8175 for it.
Best regards
Frank
What about just having a preview version link of your application switch to the WiseJ version? Kind of like the old Azure portal vs the new one?
We are in exactly the same boat and that is the sort of route we are going if we need to ship early but we are shooting to have our app converted in a month.
IIS is money-costly and we want to remove dependence from it as soon as possible
Yep, it’s a known issue: WJ-7268. We don’t have a solution yet. The problem is that the button captures the pointer when pressed to detect when the user moved it away and void the click.
Related: with Wisej you can capture the pointer using the Capture property – all pointer events will go to the control that captured it.
You can have several application .json files. The name of the json is the name of the app in the url. Basically you can have multiple sub-applications (or entry points) within the same project.
If the “url” and the entry points (startup or mainWindow) in the json are unchanged, you can have multiple json files pointing to the same app.
More to the point: copy your Default.json to Debug.json and edit the settings that you want to have different. Then you can launch the debug version by adding /debug to the url.
On the server side we are looking at adding support for OWIN (including self hosting and single exe deployments with embedded chromium or IE), and FastCGI.
Also I would assume such work would be a lot easier once .NET standard 2 ships as it adds back a ton of missing .NET features.
Hi Stanislaw,
this is still on our roadmap but before we get deeper into it, we need to focus on adding
missing features first as described here:
https://wisej.com/support/question/planning-of-features
We will keep you updated on any progress to remove dependency from IIS.
Best regards
Frank
Hi Veikko,
it depends a bit on how you are planning to deploy your application.
But basically you can use any technique that is available to C#/VB.NET or ASP.NET applications.
There are a lot of samples that you can found with google.
Here is one of them: https://www.codeproject.com/Articles/823854/How-to-connect-SQL-Database-to-your-Csharp-program
Hope that helps,
Best regards
Frank
I’m using the latest build (1.3.44). However, the bug appears to be gone now. I deleted the “.vs”, “bin” and “obj” directories and rebuilt the solution. Looks like it works now. Not sure what caused it.
