Global Usings Support about bflat HOT 3 CLOSED

Also, I'm happy bflat works for your sample!

I'll find time to run through the instructions and send any feedback. I'll also link it from this repo/docs!

from bflat.

I'll leave this without a first class command line switch - global usings can be placed in a file like you're doing now.

from bflat.

I could expose a command line argument to inject individual global usings, but I wouldn't go as far as hardcoding the list from the .NET SDK - two reasons:

• The list is not stable and I'm not looking for more things I need to keep in sync
• I don't particularly agree with the selection of things that are default-included. The only thing I could maybe agree on is the System namespace, but the rest is just junk that pollutes the global namespace (it takes away "good" identifiers such as Path, Task, etc. that people should be able to use for their own things). I fought pretty hard to avoid having this to be the SDK default. It's default for new projects only. I pretty much always just delete the <ImplicitUsings>enable</ImplicitUsings> line from my projects so that I don't have to deal with it.

I think this won't really solve it for you because it would just make the bflat command line invocation longer.

from bflat.