-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
Start point.
Write macros to generate BLToolkit's properties and attributes in empty model classes. Properties are generated by tables or by macros arguments.
Requirements to start: Write an abstraction for DB schemes supported by BLToolkit. (It can be done as a part of BLToolkit if IT agrees.) Introduce application configuration, at least connection parameters. Introduce a rule for class namings and table namings connection for different DBs.
The stage has been completed when we need only to create a corresponding class in the project to work with a needed table. The connection between tables is not required in this stage.
If somebody doesn't know what is it - http://flux88.com/blog/net-database-migration-tool-roundup/. Here we have to implement DSL for DB migrations (It could be a part of toolkit). It would be good if DSL could automatically create undo at least for simple situations.
The stage has been completed when we can easily create and run migrations. Integration with Visual Studio is not required but can be done simultaneously.
In this stage we want to generate navigation for View, Controller, Action and other standard URLs without using "magic" strings.
Without diving into details, this we need
* Views.Home.Index or Views.Index just retures a View string * Controller.Home.Index(par1, par2) must return action descriptor for URLs creation. * Action.Index the same for the current controller.
The same is done in MVCContrib via T4.
The stage has been completed when all is generated without human touch. Any other HTML helpers can be written simultaneously.
Here we have to remove ViewModel classes. Saying correctly make them invisible for the programmer, their fields would be declared in the controller by macros
Not sure if this is possible yet.
See subject. Beta stage. In this stage no development is planned.