We are deeply regret for the long delay in getting back to you.
We have validated the reported runtime exception in various production server environment like Azure, Windows server 2016, etc.. And we suspect that the issue occurred due to below cause when deployed in production server.
1. The production server may have outdated configuration like .NET Core SDK and .NET Core runtime hosting bundle.
Solution: Update your dotnet hosting bundle with latest version in your production machine.
Please find the link below for latest hosting bundle and install it in your hosting machine to resolve this.
2. Under the Application Development Roles in your production/deployment machine, ensure the following options are checked
- ASP.NET 4.6
- WebSocket Protocol
Meanwhile we have handled the runtime null exception in our source and the fix is available in the below NuGet package. This will be included in our upcoming SP1 Release which is expected at the end of January 2020.
Before installing the above nuget, please clear your local nuget cache by using below command.
"dotnet nuget locals all --clear"
In Visual Studio, Click TOOLS -> Nuget Package Manager -> Package Manager Settings. Find the button "Clear All NuGet Cache(s)"
If you are still facing the same issue, then please provide us the below details of your production machine/deployment server.
- .Net Core SDK version
- .Net Core Runtime version
- Share the details by running 'dotnet --info'
It will helpful to provide the better solution to resolve this as soon as possible.
Please let us know if you need any further assistance on this.
Jesus Arockia Sankaran S