Blazor
Hans Karlsen (talk | contribs) (Created page with "Initial tests on MDriven - via .netStandard2.1 to run on Blazor. WCF-Client is not supported https://github.com/aspnet/Blazor/issues/598 - I will remove WCF dependencies in n...") |
Hans Karlsen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Initial tests on MDriven - via .netStandard2.1 to run on Blazor. | Initial tests on MDriven - via .netStandard2.1 to run on Blazor. | ||
WCF-Client is not supported https://github.com/aspnet/Blazor/issues/598 - I will remove WCF dependencies in new build set called MDriven.netStandard.Blazor | WCF-Client is not supported https://github.com/aspnet/Blazor/issues/598 - I will remove WCF dependencies in new build set called MDriven.netStandard.Blazor. | ||
We use System.Runtime.Serialization.Formatters.Soap.SoapFormatter to handle serializing of complex keys (think it is overkill and should work away). SoapFormatter does not work in Blazor. Replacing this with dummy stub initially - only in MDriven.netStandard.Blazor builds. | |||
Revision as of 07:35, 3 November 2018
Initial tests on MDriven - via .netStandard2.1 to run on Blazor.
WCF-Client is not supported https://github.com/aspnet/Blazor/issues/598 - I will remove WCF dependencies in new build set called MDriven.netStandard.Blazor.
We use System.Runtime.Serialization.Formatters.Soap.SoapFormatter to handle serializing of complex keys (think it is overkill and should work away). SoapFormatter does not work in Blazor. Replacing this with dummy stub initially - only in MDriven.netStandard.Blazor builds.
This page was edited 39 days ago on 03/26/2024. What links here