I use . separation – for example EmployeeController.SomeSpecialBehaviour.cs. I also link it into the project tree via “dependentUpon” or whatever it is in the csproj, so that it nests under the file (in solution explorer) neatly. You have to do that by hand (edit the csproj) or with an addin, though; for example: <Compile Include=”Subfolder/Program.cs” … Read more
Here is the solution I have been using for such cases. It is useful when you have auto-generated classes that you want to decorate with attributes. Let’s say this is the auto-generated class: public partial class UserProfile { public int UserId { get; set; } public string UserName { get; set; } public string Firstname … Read more
If your problem really is just working with a large class in an editor, the first solution I’d actually look for is a better way to break down the problem. The second solution would be a better editor, preferably one with code folding. That said, there are a couple of ways you might break up … Read more
No, you cannot have two partial classes referring to the same class in two different assemblies (projects). Once the assembly is compiled, the meta-data is baked in, and your classes are no longer partial. Partial classes allows you to split the definition of the same class into two files.