David Kean

@nguerrera This was cause of your issue when you tried to do this.

Okay, thinking about this a little more I understand why they originally implemented this behavior - but I don't agree with the fix they made. Basically, they wanted to prevent...

@mne91 Yes, closing the solution and reopen after removing the "Custom Tool" for the language-specific ResX (neutral can still have Custom Tool) in the properties windows. Basically, the legacy project...

Remove the Custom Tools "PublicResXFileCodeGenerator" from the Resource.en-US.resx, and reload the project. You will not see the error again.

@Latency ResX isn't deprecated. Did the [workaround](https://github.com/dotnet/project-system/issues/1553#issuecomment-397600474) not work for you?

Reloading a project will never reuse, and would require a significant change and rewrite on how this works. This would be better fit into Dev18 where the communication layer will...

These are currently tied to a IVsHierarchy instance that cannot be changed and Roslyn will need to be updated to handle this transient state. A project also doesn't have context...

I would separate the two states; configuration-switch and project-reload. We don't need a bunch of plumbing for the former, we do for the latter. If we block on this plumbing,...

I would verify that this is actually us restoring, or whether its the command-line restore running in-proc/.

If its the command-line there's nothing the project can do to suppress it.