All Answers

Hi Steve,

You can go to https://wisej.com/builds , for download our latest build and install it .

When licence will be requested just enter the license key.

Best,

Kevin (ITG)

Hi Robert,

We have a control UserComboBox, with this you can create any dropdown style

Doc: https://docs.wisej.com/docs/controls/lists/combobox/usercombobox

Sample is in attachment.

Happy coding,

Kevin(ITG)

Right, so 100 unique browser sessions is what the Pro server license allows?

Hello Luca,

how do I access the Github: https://github.com/iceteagroup/wisej-ext-kendo

I am interested in implementig a kendo grid.

Second sample:

WisejWebPageApplicationIISExpress.zip

It’s the same project using the modified launchSettings.json as above and web.config updated for IIS Express to support .NET Core. This one can only debug .NET 6 because of the changes in web.config. It’s also possible to re-add support for running .NET 48 in launchSettings.json and duplicate web.config.

First sample:

WisejWebPageApplicationStandard.zip

It’s the unmodified project templates for VS 2022 and Wisej 3 for .NET 6. It can run both .NET 48 and .NET 6.0 just by switching the target. See zip and images attached.

It’s detailed here: https://docs.wisej.com/license/license-model-2022/server-licenses#concurrent-clients It’s also linked on each item in the price list.

In short, it’s the workload. Logged in users is an application specific feature. Wisej.NET only knows about browser sessions,  unique browser/clients, and concurrent requests.

You don’t need to do that. We’ll send two samples shortly:

1- Using the project as-is to debug at the same time net48 (iisexpress) and net6.0 (aspnet core hosting = kestrel)

2- Project modified to debug net 6.0 using iisexpress without editing the project (must use the iis aspnet core integration)

Thank you for the pointers, though, this does not change much. Starting the app nothing happens, albeit no exception is thrown. I still have to do some research on my own. I just started using .Net Core.

For now, I start the project with net48;net6.0, open all my windows in the designer, switch to net6.0;net48 and happily code away. This way, IIS Express works and the designer continues to work.

Cheers, Gerhard

I have added this to launchSettings.json

{
 "iisSettings": {
 "windowsAuthentication": false,
 "anonymousAuthentication": true,
 "iisExpress": {
 "applicationUrl": "http://localhost:54018/",
 "sslPort": 44372
 }
 },
 "profiles": {
 "IIS Express": {
 "commandName": "IISExpress",
 "launchBrowser": true,
 "environmentVariables": {
 "ASPNETCORE_ENVIRONMENT": "Development"
 }
 }
 }
}

And removed web.config. It works without altering the order of the targets. However in this case you can only run .NET 6 in IIS Express. If you keep web.config it gets confused and VS keeps adding the IIS native integration with ASP.NET Core breaking IIS Express.

That is why we have configured the Wisej 3 projects to run one profile “Application Name” that can run both .NET 48 using IIS Express and .NET 6 using the native Kestrel. ASP.NET Core apps are served through kestrel and are usually always self hosted.

When deploying in IIS you have the option to un inprocess or out of process. In both cases you need to install the ASP.NET Core IIS integration native handlers (it’s documented in MSDN in a very confusing way but you can find a good reference on our deployment book). Either way it goes through the OWIN middleware. There is no more pipeline for .NET 6.

Our project templates are configured to allow using both at the same time.

Please note that if the IIS ASP.NET Core handlers are added to web.config (and VS has a tendency to do it by itself) then IIS (including Express) cannot use .NET 48 anymore

Hi Nicholas,

We’re currently investigating the issue and we’ll get back to you as soon as possible!

Best,
Alaa

//

Anything the works in JavaScript should be fine. We don’t have anything different than what is available. If you find a different solution let us know.

Thanks for write us

We are working hard to have soon learning documentation about it

Regards

Hi

Thanks for write us

yes. they are also available for the community license (they show a watermark at design time and an alert at runtime).

Here you can see our license model

Licenses Model 2022 – Developer Licenses

HTH

Hi Page,

You can get the extension there and build it : https://github.com/iceteagroup/wisej-extensions/tree/3.0/Wisej.Web.Ext.PrintPreview,

We have not yet released the extension.

Happy coding,

Kevin (ITG)

Hi, I’m using 3.0.6, but I think other versions will have the same problem, because there is no NuGet package for Print Preview

https://www.nuget.org/packages?q=wisej+printpreview

Hi Luca,

I solved using

var me = this;

and on events I call the webmethod like me.WriteToScreen(“CONNECTED”);

Thank you for your quick response.

Regards

Hi Luca,
well, it seems I still miss something…
As you said the UseStartup is deprecated in .net 6. However, the default Wisej3 project template creates a Startup.cs, which includes the app.UseWisej();

According to Microsoft docs, https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60?view=aspnetcore-6.0&tabs=visual-studio#smhm
if one wants to use a Startup, one has to instantiate the Startup class like
var builder = WebApplication.CreateBuilder(args);
var startup = new Startup(builder.Configuration);
startup.ConfigureServices(builder.Services);
var app = builder.Build();
startup.Configure(app, app.Environment);
app.Run();

Such a reference to Startup is not included in the Wisej3 project’s Program.Main, which is defined as the entry point in default.json.
Moreover, the build action for the Startup.cs is set to Content, NOT to Compile (I found this the hard way, when I excluded the Startup.cs fro the project, then re-inluded it and the action was set to compile but there were build errors everywhere after that).

So, how is app.UseWisej() called? It is certainly not hit if I set a break point.

Best,
Alex

Wisej 3 doesn’t override 2.5, the two are unrelated having different assembly versions. Wisej is not installed in VS 2019 or in VS 2022. The Wisej.Framework.dll assembly comes from nuget. The designer is registered in the GAC isolated by AssemblyVersion – it’s all standard .NET that we cannot change in any way and it’s the same for any assembly of any kind.

If the C# compiler doesn’t recognize an assembly it means it cannot load it. Check the nuget reference or remove the nuget and reference wisej dll directly.