Christophe Gijbels
Christophe Gijbels
@avanderhoorn For WebForms to make the PRG work (and for a lot of other issues as well), we need to change the definition of when the `EndRequest` on the `GlimpseRuntime`...
I also merged the latest version of master with version-2 and solved some merge conflicts. Now that this is done, TeamCity is actually picking this PR back up for an...
The build succeeded in the meanwhile Oh, as a side note, I already did the reverse integration with master, since we decided to rebase #686 on version-2 instead of master,...
I've checked in a little breaking change regarding the framework providers. - The `GlimpseRuntime.IsInitialized` is renamed to `GlimpseRuntime.IsAvailable` - The `GlimpseRuntime.Initialize(...)` must be changed to `GlimpseRuntime.Initializer.Initialize(...)` The `GlimpseRuntime.Initializer` also allows...
@avanderhoorn I'm not quite following you when you say > I wonder if this could be also rigged to work to buffer messages are are sent prior to Glimpse init?...
@avanderhoorn I was talking about plain log messages. We had some code commented out in the `HttpModule` static constructor, because the `Factory` got removed, hence no option any longer to...
I added another breaking change because I removed the `GlimpseRuntime.ExecuteDefaultResource()`, framework providers should now call the `GlimpseRuntime.ExecuteResource(...)` and just pass in the resource name if available and otherwise null. If...
@grahammendick Yep, that is the idea, because the change needed for that is relative small (see this [POC PR](https://github.com/Glimpse/Glimpse/pull/606)) and it would not only support the typical PRG pattern but...
@avanderhoorn I think @nikmd23 has a different view on that, from what I remember from our talks is that he wants to prevent as much as possible (if possible of...
V2 changes don't fix the initial reason why this failed, although many other changes will prevent an exception to occur. So keep it open so that I don't loose track...