Wisej.NET 3 introduces a new approach for creating and working with projects based on ASP.NET Core. The changes include a new , Kestrel Web Server, and more.
There is no need to change the project format if you are staying with .NET 4.8! Wisej.NET 3 supports both .NET Framework and .NET Core. You only need to change the project format to the SDK format if you are going to use .NET Core and ASP.NET Core.
The Basics
Change Project Format to SDK
When migrating a Wisej.NET 2.x project to Wisej.NET 3, it's notrecommended to change the existing project but rather create a new Wisej project using the new templates and copy over files.
Moving from older versions of Wisej.NET to Wisej.NET 3 requires updating the project to the new SDK Project format.
Take note of all embedded resources, references and build customizations within the Project.
6. Add embedded resources, references, and build customizations back.
Files that are Embedded Resources are reset to Content, don't forget to set them again to Embedded Resource.
Upgrade Resource Files (.resx)
All the localization .resx files need to be upgraded to Wisej.Framework, Version=3.0.0.0. It's a simple task that can be completed using Visual Studio Search & Replace.
Replace "Wisej.Framework, Version=2.0.0.0" with "Wisej.Framework, Version=3.0.0.0".
It's likely that your projects don't have any Wisej.Framework reference in the .resx files.
Add Startup.cs
A Startup.cs file is required for ASP.NET Core projects (Wisej projects targeting .NET Core).
Right-Click the Project.
Click Add > Class.
Set the name to Startup.cs.
Click Add.
Copy the following content into the Startup.cs file or download the file below.
using Microsoft.AspNetCore.Builder;
using Microsoft.Extensions.Configuration;
using Wisej.Core;
namespace $safeprojectname$
{
/// <summary>
/// The Startup class configures services and the app's request pipeline.
/// For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940.
/// </summary>
public class Startup
{
public Startup(IConfiguration configuration)
{
Configuration = configuration;
}
public IConfiguration Configuration { get; }
public static void Main(string[] args)
{
var builder = WebApplication.CreateBuilder(new WebApplicationOptions
{
Args = args,
WebRootPath = "./"
});
var app = builder.Build();
app.UseWisej();
app.UseFileServer();
app.Run();
}
}
}
Imports Microsoft.AspNetCore.Builder
Imports Microsoft.AspNetCore.Hosting
Imports Microsoft.Extensions.Configuration
Imports Microsoft.Extensions.DependencyInjection
Imports Microsoft.Extensions.Hosting
Imports Wisej.Core
''' <summary>
''' The Startup class configures services and the app's request pipeline.
''' For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940.
''' </summary>
Public Class Startup
Public Sub New(configuration As IConfiguration)
Me.Configuration = configuration
End Sub
Public ReadOnly Property Configuration As IConfiguration
Public Shared Sub Main(args As String())
Host.CreateDefaultBuilder(args).ConfigureWebHostDefaults(
Sub(builder)
builder.UseWebRoot("./")
builder.UseStartup(Of Startup)()
End Sub).Build().Run()
End Sub
'' This method gets called by the runtime. Use this method to add services to the container.
Public Sub ConfigureServices(services As IServiceCollection)
End Sub
'' This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
Public Sub Configure(app As IApplicationBuilder, env As IWebHostEnvironment)
app.UseWisej()
app.UseFileServer()
End Sub
End Class
Don't forget to update the Namespace.
Add launchSettings.json
Wisej 3 projects targeted for .NET Core require adding a launchSettings.json file to the /Properties directory of the project.
Right-Click the project on the \Properties folder.
Profiles define the startup behavior for the application. Don't forget to update the profile names.
Project Properties
The new SDK project format has many properties that are not available in the project property panel. You have to get used to editing the .csproj or .vbproj files directly.
Unfortunately, there isn't a comprehensive list anywhere and many properties are not standard and depend on build targets. All you can do is search around...
These are just a few that we have added to our templates:
Implementation Changes
With the release of Wisej.NET 3.0, which is the first version to support both .NET Framework and .NET Core, we have standardized all classes to ensure compatibility across these two environments. This means that any class differences between the two have been reconciled, and unique classes from either environment have been seamlessly integrated.
UITypeEditor
Originally, the class System.Drawing.Design.UITypeEditor was utilized. However, because it does not exist in .NET Core, we have reimplemented it as Wisej.Web.UITypeEditor.
Therefore, attributes that were previously declared as [Editor(typeof(MyEditor), typeof(System.Drawing.Design.UITypeEditor))] must be updated. You can now specify them as [Editor(typeof(MyEditor), typeof(UITypeEditor))] or [Editor(typeof(MyEditor), typeof(Wisej.Web.UITypeEditor))], depending on the namespaces defined in your using directives.
Http* Types
Previously, all Http* types were located in the System.Web namespace. However, in .NET Core, these types differ significantly. To address this, we have reimplemented a unified Http type system under Wisej.Core.Http*. This ensures consistency and compatibility when working across different .NET environments.
When transitioning from System.Web classes, you will likely encounter compilation errors, making it straightforward to identify where these classes are used in your code. Typically, these classes are utilized in the Upload control, within any implementation of the IWisejHandler interface, and in managing cookies collections. Identifying and updating these areas will be essential to ensure compatibility with the new system.
