The upper right side of the window shows the current generated POCOs, based on what is selected in the tree. The checkboxes on the tree are for picking specific objects for exporting to files. The SQL Server tree lists all the databases on that instance and each database lists its data objects - tables, views, procedures, functions & TVPs. POCO Generator also detects primary keys, foreign keys, unique keys and indexes for tables. There are 5 types of database objects that the POCO Generator can handle: The solution that I opt to create is a visual-centric stand-alone application, the POCO Generator, that traverses the SQL Server, and generates POCOs from various data objects.
There are script tools like T4 (Text Template Transformation Toolkit), which Visual Studio supports. The tool detects changes to the database and generates the appropriate POCO classes. This may be good for introductory/one-or-two classes scenarios, but is not applicable for production. There are plenty of ways to generate POCO classes from a database. Go to packages\ILMerge.\tools, right-click on ILMerge.exe and open the properties window. exe files from other computers and block them, so when you tried to compile the code, Windows stopped ILMerge from running and the whole thing failed. If you downloaded the source code, failed to compile it and got an error regarding ILMerge, then you need to unblock ILMerge.
