Still not building, but getting very close now (< 30 errors left). Added request-scoped CancellationToken support for server commands, fine-tuned the base implementation a bit, added derived concrete commands for most console notifications and requests, will resume tomorrow.
Also split up RpcMethodNames into small nested classes, separating LSP from LocalDb and Shared names
(and then further by category e.g. ServerLifeCycle)
@FreeMan the only thing I see that needs the host process to shut down (or at least RD add-in cleanly unloading) is updating the add-in client. Might be useful to make a "Rubberduck Updater" app that tracks what's installed vs what's available - would move the version-check out of RD itself.
That said I always find it funny when you update VS and then the first thing that happens is that the updater app updates itself
Hm you could choose to skip installing the updater to opt-out of RD update notifications
Anyway, deployment and updating is pretty far down the road
Ha and we could have a "welcome" editor tab (that could also be opted-out) that's opened when the client starts, to show RD news stuff (links to recent articles, recently-modified website content, "getting started" and "release notes" links, etc.
> What's new in Rubberduck 3.1
damn
would make a good proof-of-concept for non-document editor tabs
could be used for displaying feature help from the website API (e.g. inspection details/examples, or how to use a particular refactoring, or what's there to know about annotations, etc.)
@MathieuGuindon Seems reasonable. NPP (for one) does this - it just opens the "What's New" readme in a new tab. Most browsers seem to do it as well. 99.999% of the time, I just close 'em without reading because I'm not invested enough in the product to know what all these esoteric sounding bugs are, but it's a common enough practice to not seem shocking to end users. Even Win updates will pop a dialogue offering a tour of new features.
@MathieuGuindon Also, my point was, don't make me download and install the LSP Server, and the DB server, and the logging server and the... if I've been out for a 3 week vaca and I'm just now getting back to see the blessed flurry of activity I missed. Just one "hey there are update(s), wanna install?" prompt & install process.
Yeah I'm thinking patches might make it easier to update locked-down machines
Politically speaking
Meaning, it'll be easier for IT to approve updates when the update isn't going to tweak any registry key or do anything new
Only the add-in client needs registry keys
Anyway I'm hoping to get a working local build some time this week; I'll push the new & improved structure and start implementing the actual database server. Can't wait!!
VBA Rubberducking
VBA Rubberducking