Factor generated code

[GoogleCodeExporter]

Rather than generate into four files (functions,enumerations,et cetera) we 
should produce code out of the generator that conforms to our 
'one-file-per-class' policy. This will aid in navigation and debugging (because 
you won't need to open massive source files).

Original issue reported on code.google.com by josh.petrie on 15 Nov 2010 at 4:48

[GoogleCodeExporter]

Actually, while developing, It us MUSH faster to have them in a single file, 
scrolling down and you can directly see and copy paste all the enmus, 
structures that are badly named mapped. It would just be a nightmare to have 
single file and to double click or open hundreds of files in VS tabs in order 
to check the names.

Also, single files means that you have to add manually the generated files... 
this is just plainly horrible, since while mapping the files, the filenames 
would change.

From my experience in generating files from my previous work, they are much 
more maintainable in a single big files rather than having them spawned in 
different files.

Original comment by alx.xo...@gmail.com on 16 Nov 2010 at 4:09

• Changed state: Invalid

[GoogleCodeExporter]

We're putting them in single files. There are solutions to all of the issues 
you raised, such as generating the .csproj's as well or augmented hand-written 
ones with custom item groups that use wildcards to collect all files in the 
generated assembly.

Original comment by josh.petrie on 16 Nov 2010 at 4:19

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by josh.petrie on 4 Dec 2010 at 9:51

• Changed state: Invalid