You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
We're seeing something rather unexpected - if we call services.AddGlimpse() but then don't call app.UseGlimpse() - for example, because we're running in a production environment - the site crashes.
The error is it appears identical to the one observed in this bug: #98
Since the call to AddGlimpse() (made in ConfigureServices) cannot be avoided by an if in an easy manner (the criteria we use which is environment is not as easily available as it is in Configure method) I would expect it to not do much until one actually calls UseGlimpse()?
Or are we expected to "pair" the Add/Use by guarding both with the same conditional (up to us to see how to achieve this)?
Differently put I am not sure if this is a bug (personally expect that it is) or me missing something...
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're seeing something rather unexpected - if we call
services.AddGlimpse()
but then don't callapp.UseGlimpse()
- for example, because we're running in a production environment - the site crashes.The error is it appears identical to the one observed in this bug: #98
Since the call to
AddGlimpse()
(made inConfigureServices
) cannot be avoided by anif
in an easy manner (the criteria we use which is environment is not as easily available as it is inConfigure
method) I would expect it to not do much until one actually callsUseGlimpse()
?Or are we expected to "pair" the Add/Use by guarding both with the same conditional (up to us to see how to achieve this)?
Differently put I am not sure if this is a bug (personally expect that it is) or me missing something...
The text was updated successfully, but these errors were encountered: