work in progress - at this stage the add-in client initializes without the legacy 2.x CW IoCInstaller class, but a bit more work is needed to refactor the menu initialization; the IServiceProvider builder will likely end up with a simple, single-method interface, perhaps with a private method for each "chunk" of dependencies. Startup reaches language server initialization, but there currently isn't any pipe I/O configured so it throws there. Ultimately the inline initialization will shift to DI,
Might be a bit wide, but settings will also be looked at in this PR; we want simpler and fewer abstractions for dealing with settings in RD3... but we'll want to retain the ability to read legacy RD 2.x settings, too.indeed, a bit wide. too wide.
work in progress - at this stage the add-in client initializes without the legacy 2.x CW IoCInstaller class, but a bit more work is needed to refactor the menu initialization; the
IServiceProviderbuilder will likely end up with a simple, single-method interface, perhaps with a private method for each "chunk" of dependencies. Startup reaches language server initialization, but there currently isn't any pipe I/O configured so it throws there. Ultimately the inline initialization will shift to DI,Might be a bit wide, but settings will also be looked at in this PR; we want simpler and fewer abstractions for dealing with settings in RD3... but we'll want to retain the ability to read legacy RD 2.x settings, too.indeed, a bit wide. too wide.Aiming for merge-ready around 04/01.