You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support Razor Pages Modules in DNN we need to deprecate the DotNetNuke.Web.Razor assembly and modules. This module pattern is not used by as much as other module types. See Migration plan for how to move forward if you have modules in this pattern
Migration Plan
If you have a DotNetNuke.Web.Razor module you will be able to migrate it to a Razor Pages Module with minimal work since they are very similar.
Reason for Deprecation
In the parent feature #2599 it cites there will be confusion between Razor Modules and Razor Pages Modules. It will be best to deprecated the old pattern as we implement a new pattern.
Description of solution
Add API deprecation warnings to all public and protected APIs
Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead
Example of DotNetNuke.Web.Razor.DotNetNukeWebPage
[Obsolete("Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead")]publicabstractclassDotNetNukeWebPage:WebPageBase{[Obsolete("Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead")]protectedinternalDnnHelperDnn{get;internalset;}[Obsolete("Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead")]protectedinternalHtmlHelperHtml{get;internalset;}[Obsolete("Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead")]protectedinternalUrlHelperUrl{get;internalset;}[Obsolete("Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead")]protectedoverridevoidConfigurePage(WebPageBaseparentPage);[Obsolete("Deprecated in 9.3.1, will be removed in 11.0.0, use Razor Pages instead")]publicdynamicModel{get;set;}}
The only additional recommended action on this is that we include specific instructions on replacement methods/calls if/when possible. Understanding that it might not be possible at 9.3.1, but should be updated as the new API's come through
@mitchelsellers I agree 100%. I am going to update the parent spec to include a deprecation note that we can maintain as the spec grows. Ideally we will have documentation in the spec in how to migrate from Razor to Razor Pages which will be relatively painless
Part of: #2599
Description of problem
To support Razor Pages Modules in DNN we need to deprecate the
DotNetNuke.Web.Razor
assembly and modules. This module pattern is not used by as much as other module types. See Migration plan for how to move forward if you have modules in this patternMigration Plan
If you have a DotNetNuke.Web.Razor module you will be able to migrate it to a Razor Pages Module with minimal work since they are very similar.
Reason for Deprecation
In the parent feature #2599 it cites there will be confusion between Razor Modules and Razor Pages Modules. It will be best to deprecated the old pattern as we implement a new pattern.
Description of solution
Add API deprecation warnings to all
public
andprotected
APIsExample of
DotNetNuke.Web.Razor.DotNetNukeWebPage
List of Deprecated Assemblies
List of Deprecated Classes
List of Affected Assemblies
Affected version
The text was updated successfully, but these errors were encountered: