We have not experienced such issue so far. Basically, we do not make any checks if the code is running in debug mode and the application should behave the same way in both cases. We also tested our .Net Core demo on Visual Studio 2017 on two of our machines but the issue was not reproduced.
The issue might be related with the environment, especially when using IIS Express as a web server. Try restarting the IIS Express to see if this would help.
The ReportResolver exception should be logged in a trace listener, if one is available. To enable tracing in .NET Core, add the following lines of code in the Program.cs
I would suggest to open a Support ticket
, so you can send us the log from the Trace Listener, as well as the project so we can investigate it on our side.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items