"One last remark: you should avoid using Task.Result and Task.Wait as much as possible as they always encapsulate the inner exception in an AggregateException and replace the message by a generic one (One or more errors occurred), which makes debugging harder. Even if the synchronous version shouldn't be used that often, you should strongly consider using Task.GetAwaiter().GetResult() instead."
learned a few things today
basically it’s pretty much impossible to do nicely
wonder if we should think about hosting our jobs that way.
next step
everything compiles
well there will be with index names
lol
but don’t think it’s quite there yet.
you can make a storage folder the trigger… so just putting the postdata there would trigger it to run.
can run C# code and it scales on its own based on triggers.
but it looks like you have to just run some c# code from a text box vs triggering a exe or being able to use full assemblies.
guess you can add nuget packages and external references
but you have to put the core logic in a .csx script file.
hmm
won’t be live until 8pm tonight
:)
time travel
I worked on an open source project with a guy in Australia once
that’s impossible
round trip time of emails is a day
so events that are being received without Count, have Count = 1?
not sure if anyone of you seen this happen, but it looks like VS started saving pdb files in my solution directory. Any idea how to make that stop?
it looks like a symbol server / symbol cache in there
so events that aren’t duplicates, just send those along without a count?