FarbKuo

like this

logging: 2017-02-14 11:17:38.5860 | ERROR | Exception calling subscriber with message of type 'Glimpse.Ado.Message.CommandExecutedMessage'. | System.NullReferenceException--未将对象引用设置到对象的实例。-- 在 Glimpse.AspNet.AspNetFrameworkProvider.get_HttpRequestStore() 在 Glimpse.Core.Framework.GlimpseRuntime.GetTabStore(String tabName) 在 Glimpse.Core.Extensions.TabContextExtensions.PersistMessage[T](T message, ITabSetupContext context) 在 Glimpse.Core.Extensibility.MessageBroker.Publish[T](T message)

I modified the custom policy,then it worded!:) ` public RuntimePolicy Execute(IRuntimePolicyContext policyContext) { // You can perform a check like the one below to control Glimpse's permissions within your application....

> I've pushed [vs2022](https://github.com/beatcracker/VSCELicense/tree/vs2022) branch which supports VS CE 2022 Preview. But as @navrozashvili mentioned, VS will only give you 15 days when you reset date in registry. I guess...

@beatcracker Where is the new key?There's not the new key you gave in my registry . 

@beatcracker @navrozashvili I have upgraded the vs2022 to 17.0.0 Preview 3.1,and I found the new key is 09478,then I modified the .psm1 file for the new key.Finally ,I ran my...

@navrozashvili so,there's no way to solve it,right?😂

@navrozashvili Maybe I should give up .Because I have reinstalled it for several times .It didn't work. 😔

@navrozashvili Finally ,I solved the problem by offline registration 🤓The link is https://blog.csdn.net/songfuliang2011/article/details/102486451 . 

> The new registry key seems to be `B16F0CF0-8AD1-4A5B-87BC-CB0DBE9C48FC` and subkey is `09560`. I have preview 4.1. I could set the expiration date when I changed the keys but still...