VB->C# removing invalid Imports

Is your feature request related to a problem? Please describe. VB ignores Imports statements which are invalid, but C# treats them as a compiler error. Old projects can have a lot of these cluttering up files from references that have been removed.

Describe the solution you'd like An option for the CodeConverter to remove these or comment them out.

Describe alternatives you've considered Search and replace, but that's an extra step.

Additional context n/a

This may be possible, either by scanning for namespace existence (being careful of casing), or by using the compiler diagnostics after conversion (but this runs the risks of issues earlier in the process snowballing). You're usually much better off getting the code 100% compiling, then running existing formatting tools