Junnark WinFormsGen 126.96.36.199 Professional Plus
WinFormsGen. Generate WinForms, Middle-Tier, Data-Tier, and Stored Procedures (or Ad Hoc/Dynamic SQL) in One Click*. WinFormsGen generates databound WinForms Objects. WinFormsGen is a combination of our WinFormsGen engine (generates Windows Forms) and AspxCodeGen 4.5 engine which generates Middle-Tier, Data-Tier, and Stored procedures or Ad-Hoc/Dynamic SQL codes. Generated WinForms are bound by strongly-typed middle tier objects that encapsulates data-tier functionalities. Objects generated by AspxCodeGen 4.5 engine are called by the generated WinForms, and can be used as stand-alone API.
Click the “Generate Code…” button.
Retrieve Microsoft SQL Server Database information.
Generate a database-bound Window Forms (WinForm) Application. The winform application is generated so you can run it and see the generated code in action.
Generate Front End (UI – Presentation Layer) WinForms (Windows Form). See more
Generate Middle-Tier Class Files (Middle Layer). See more
Generate Data-Tier Class Files (Data Layer). See more
Generate SQL Scripts (Stored Procedures or Ad-Hoc/Dynamic SQL in Class Files). See more
Generate other classes, app.config, etc. (not shown in the diagram). See more
Generate Stored Procedures in your database (Microsoft SQL Server), or, generate Ad-hoc/Dynamic SQL Class Files. See more
N-Tier Layer Approach
WinFormsGen generates code in a 3-tier (n-tier) architecture. A presentation tier (winforms – the client), middle tier (business objects), data tier (data access objects), and the database scripts such as stored procedures or a-hoc/dynmamic sql. Code is separated in different layers, see below:
Front End (UI – Presentation Layer) Windows Forms. See more
Middle-Tier Class Files (Middle Layer). See more
Data-Tier Class Files (Data Layer). See more
SQL Scripts (Stored Procedures or Ad-Hoc/Dynamic SQL in Class Files). See more
The generated middle tier objects (and data tier objects) can be put in another project and consumed by other clients. Clients could be a web form (.aspx), a win form, or a web service (.asmx, wcf), etc.
The middle tier encapsulates all calls to the data access objects (data tier) so that calling a CRUD (create, retrieve, update, delete) and other operations are very easy and may only take one line of code for most parts. We made it even easier by generating and showing an example for each CRUD operation, for each table in your database, so you just copy and paste a call from your chosen client.
The data tier encapsulates all calls to the database. These could be calls to Stored Procedures or Dynamic SQL. Stored Procedures or Dynamic SQL are also generated so you don’t have to worry about writing T-SQL commands.
Listed below are quick descriptions of the Windows Forms WinFormsGen generates that makes up the Presentation Layer (Front End). Note: All generated winforms with a grid also have paging and sorting functionality. CRUD are database operations which means: create (add a new record), retrieve (get an existing record), update an existing record, delete an existing record.
Listed below are quick descriptions of the Business Object class files WinFormsGen generates that makes up the Middle Layer (Middle Tier). In a 3-tier infrastructure, middle layer code is called by the UI or presentation layer code. It can contain business computations applicable to the application’s purpose. It also contains calls to the data layer code.
Accessing Code From a Client
Although WinFormsGen can generate Web API code both for public or private consumption, you may also elect to remove the middle layer code and move it to a Class Project so you can share it with other applications. Here are some code examples on how a windows-based client such as an MVC web app, web forms, win forms, web service (.asmx, wcf), etc can access the API. The examples below shows how to call the generated Middle Tier code from a client.
Note: We made it even easier by generating all the code examples for each of the method that you can access. More operations can be called as shown here, and these operations are generated for each of your database table.
Because everything else is generated for you, all you have to write is the following code. We made it even easier, we also generate examples for each operation, so all you need to do is copy and paste code like the ones showing below. So if everything here is already generated why would I need to write any of these code? There could be many scenarios that you may need to access already generated operations. For example, you may need to access these operations when you add new pages or even new classes in your application. Another scenario could be that you have an Error table where you log errors in the application, you can add a logic in the Global.asax that saves the error to your table, a few lines of code and you’re done. You can also bundle operations in a button click, for example you can add a new item in one table and then update another table in one click. There could be a gazillion scenarios why you would need to write these code.
Accessing Code From the Middle Tier
To make it really simple, the Data Layer method signatures are very similar to the Middle Layer method signatures, we simply add a string constant “DataLayer” to the middle layer method name to call data layer objects. For example if the middle tier object name is Categories, then the respective data tier object name is CategoriesDataLayer. To call a data layer method you simply add a dot and then the method name; e.g. CategoriesLayer.TheMethodName();
Listed below are quick descriptions of the Data Layer class files WinFormsGen generates that makes up the Data Tier. In a 3-tier infrastructure, data layer code is called by the middle layer code. It contains calls to the database (stored procedures/ad-hoc or dynamic SQL).
WinFormsGen, generated, Middle, Layer, middle, generates, Generate, Stored, WinForms, layer, Dynamic, objects, database, Class, Files, Procedures, operations, below, engine, method, WinFormsGen, generated, Middle, Layer, generates, Generate, middle, layer, Dynamic, WinForms, Stored, Class, database, objects, Procedures, operations, Files, table, method, access