Niels Swimberghe
Niels Swimberghe
Publishing and maintaining multiple versions because other hosting services aren't compatible won't be manageable for us. Microsoft's recommends using isolated hosting, because these kinds of issue happen all the time....
I see, is there an issue you can point me to for the problems with Twilio and isolated hosting? I'd like to help if I can.
Agreed, it would be great to be able to define the col-groups for other breakpoints.
@waynebrantley System.Text.Json is supported on netstandard2.0 too, so the Twilio library should be able to use those APIs on all supported versions of .NET, except for .NET Framework 3.5. .NET...
@waynebrantley I don't have visibility on that as a former Twilion, but I don't expect this to be done anytime soon.
> We tried to address this issue in version 7.0.0 however this issue (#732) came up as people were still using previous versions. Removing .NET Framework support doesn't make sense...
@tiwarishubham635 That's odd. I have created a GitHub issue for them to clarify this. https://github.com/dotnet/docs/issues/41005
They updated the docs. The support is .NET Framework 4.6.2+
I'm trying to use Blazor WASM inside a Chrome extension and I can't reroute all requests to index.html. Hash routing would be helpful.
@rajsite I would recommend using the default routing, and only use hash routing if you can't avoid it. I guess we can't use hash routing atm anyway. You can deploy...