If you're not looking commit-by-commit this might look odd, butTryAddImportsToContainedDocument used to always throw, therefore the rest of this method was unreachable, therefore this wholeAddImports method never did anything, which then meant theAddReferencesAndImports that called it also never did anything.

I'm guessing there are no snippets that add usings in VS for Mac??

@Therzok@DavidKarlas@KirillOsenkov Does that make sense? Is this an extension point for VS for Mac? (not that I can see how it worked if it is)

I'm guessing it was copied from here but we had no impl due to MonoDevelopWorkspace being in MonoDevelop, not platform assemblies:

@davidwengier yes that make sense, no snippet inserts usings so I think its fine to delete this.

Shouldn't both of these be_camelCase (or am I missing some naming convention rule)?

If it's protected, we tend to do this style since it's acting more like a property.

@Youssef1313 I found this surprising too, but these were mechanical changes driver by the Roslyn .editorconfig rules so who am I to argue ¯\_(ツ)_/¯

Looks likeprotected readonly is PascalCase andprotected is camelCase with underscore. It doesn'tnot make sense, I guess, but its a good reminder of why we should all have personal projects we can escape to, with sensible rules :)

Are we able to do this to the VS layer at the same time, since the annotations are likely the same?

(I'm actually not sure if we can just unify this file, since it seems like it doesn't have any dependencies and each side inherits it appropriately.)