-
Notifications
You must be signed in to change notification settings - Fork 0
Compatibility: 3rd Party Components
CoreForms provides basic runtime support for libraries that are compiled for .NET Framework. Depending on the library you are using, this might work flawlessly or not at all.
Generally speaking there are two broad categories:
- Control libraries can work if they don't use any unsupported features and use clean exception handling (see thread-abort sematics above)
- Infrastructure-level libraries, such as authentication handlers, should probably be replaced with .NET Core versions
Aside from the various standard references for CoreForms, you need to add the following dependencies when working with third-party libraries:
<PackageReference Include="CoreForms.Web.ApplicationServices" Version="7.0.0-alpha.1" />
<PackageReference Include="CoreForms.Web.Design" Version="7.0.0-alpha.1" />
<PackageReference Include="CoreForms.Web.DynamicData" Version="7.0.0-alpha.1" />
<PackageReference Include="CoreForms.Web.NetFrameworkBridge" Version="7.0.0-alpha.1" />
Please note that these tests are based on samples and give a general idea of what to expect.
We have had successfully tried Telerik UI for ASP.NET AJAX and looked through thread-abort semantics without finding any obvious issues.
Syncfusion Essential for ASP.NET Web Forms is likely compatible with CoreForms v7.0. (Note: CoreForms v6.0 is not compatible)
ASP.NET Web Forms Controls: No practical experience
Ultimate UI for ASP.NET Web Forms: No practical experience
ASP.NET Ajax Control Toolkit requires postprocessing via the DesignerAttributeRewriter. Thread abort semantics have not been verified.