Using non-default packages in BridgeMessenger

[v-p-b]

I need some packages in my BridgeMessenger, but I can't use the using directive in the code, because these directives are inserted at a place where using is illegal during Launcher compilation (see https://docs.microsoft.com/en-us/dotnet/csharp/misc/cs1529 ).

How can I use packages like System.Net.Http or Newtonsoft.Json in my BridgeMessenger?

Edit: Another problem that came up is that even when I edit Grunt templates to include the appropriate using directives, the compiler doesn't seem to find the requires assemblies, although they are added to the Covenant project.

[v-p-b]

OK, this is what I figured out so far:

1. Data/Grunt/GruntBridge/GruntBridge.cs must be extended to include the relevant using directives. I had to recreate my DB after this was done. Making this configurable seems to require adding a new remplacement token to the template.
2. Core/Common.cs must be updated to include the required assembly references in the defaults for Roslyn. (This could be done easily during runtime based on user input)
3. The assembly DLL's must be copied under Data/AssemblyReferences (what is the proper way to obtain these for different framework versions?).
4. ???

Edit: Now I realize, that relying on non-default packages will break Grunts when executed on target systems (without those dependencies installed). However, it still seems useful to provide a way to dynamically add using directives to support the use of namespaces present in default assemblies, but not used by the original templates.

[cobbr]

Hey @v-p-b , apologies for the late response. Yeah, it's going to have to be unsupported at the moment to include non-default assemblies in a user friendly way. This technically can be done if you do some sort of manual Assembly.Load on the assemblies before using them, however.

I'll think about adding support for using directives, but for now you will just have to specify the full namespace for each use.