MVC-styled controller actions - change to move from using IChromelyRequest, IChromelyResponse as controller action request/response wrappers. Developers can now define their own action arguments and response types.
Basic types are supported:
This is extensible by implementing and registering a IChromelyModelBinder.
A similar approach has been previously implemented by @RupertAvery - Chromely.Mvc.
This is also implemented in EdgeSharp.
Controller base renaming - to avoid conflict with AspNetCore Owin Mvc controller naming, Chromely base controller will be renamed ChromelyController.
Resource folder url scheme: Currently the UrlSchemeType "Resource" maps to a relative folder in the application folder. Based on https://github.com/chromelyapps/Chromely/issues/244, UrlSchemeType "Resource" type will be split into:
LocalResource: this does what the current "Resource" do, using app relative path.
FolderResource: this allows host names to be mapped to actual folder path.
e.g., "E:\img" can be mapped to "http://img"
The only requirement is to register the Url schemes:
Version 5.2 upgrade begins a gradual code base move to .NET 6.
Source - https://github.com/chromelyapps/Chromely/blob/master/src Demos - https://github.com/chromelyapps/demo-projects
Comments are welcome.
Planned/implemented
Move to .NET 6.
AspNetCore Owin support - this implements a new library - Chromely.Owin and is an implementation of @amaitland Chromium.AspNetCore.Bridge. It is in essence a migration of Chromely.AspNetCore.Mvc.Example. There is also a similar implementation in EdgeSharp.
MVC-styled controller actions - change to move from using IChromelyRequest, IChromelyResponse as controller action request/response wrappers. Developers can now define their own action arguments and response types. Basic types are supported:
This is extensible by implementing and registering a IChromelyModelBinder. A similar approach has been previously implemented by @RupertAvery - Chromely.Mvc. This is also implemented in EdgeSharp.
Controller base renaming - to avoid conflict with AspNetCore Owin Mvc controller naming, Chromely base controller will be renamed ChromelyController.
Resource folder url scheme: Currently the UrlSchemeType "Resource" maps to a relative folder in the application folder. Based on https://github.com/chromelyapps/Chromely/issues/244, UrlSchemeType "Resource" type will be split into:
The only requirement is to register the Url schemes:
Nice to have: