Roslyn: Shared project model

[mkrueger]

I got this bug report:

---

Added a second class in same .cs file.

namespace stuff
{
class1 { }
class2 { }
}

When adding additional class in same .cs file, VS4Mac suggested moving class2 it’s own file. Instead of creating new class2.cs in existing file’s project (in this case the shared code project of the Xamarin Forms project), it moved to iOS specific project.

Basicaly the MoveTypeToFile refactoring moves the class to the project the shared project is associated with. Roslyn has no representation for shared projects ATM and I don't see any way to fix that - and it may affect more refactorings like generate type and so on.

Would be nice if that could be fixed in future versions.

[zspitz]

This is probably the same probem. (IIRC there's a corresponding issue here on GitHub, but I can't seem to find it now.)

[DemetrisLeptos]

the problem with SharedProjects and MoveTypeRefactoringProvider still persists - it actually crashes now - not even moving to a concrete project