I'm generating the bulk of my ASP.NET MVC scaffolding code. All generated files are partial classes which use standard naming conventions. For example, my employee controller file is named EmployeeController.cs. If I wish to extend the EmployeeController with custom, non-generated logic, I create a second partial class file named EmployeeControllerCustom.cs. I separate the custom and generated logic into two different files so the next time I generate the EmployeeController my custom changes aren't overwritten. Adding the "Custom" suffix to the file name seems reasonable to me, but is there a more established partial class file naming convention which I should be following?
. 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="Program.cs" /> <Compile Include="Program.Foo.cs"> <DependentUpon>Program.cs</DependentUpon> </Compile>
To add to Marc Gravell♦'s answer, I had a situation with files in a subfolder and the
DependentUpon node being ignored. The short of it is that in such a case it my xml had to be:
<Compile Include="foo\bar.cs" /> <Compile Include="foo\bar.baz.cs"> <DependentUpon>bar.cs</DependentUpon> <!-- Note that I do not reference the subfolder here --> </Compile>
I hope this helps someone :)