When I got into .Net everyone was saying how you had to make your datatier. I took that to mean a set of classes to handle getting and putting data from/to the database(s).
In 2005, it seems Microsoft takes care of that for you. You create a datasource of your database and Visual Studio creates a perfect replica of the database as a dataset and creates a tableadaptor (custom class) for each table. Sounds great and seems to work well.
This weekend I was stumbling around online for development tools and came across www.mygenerationsoftware.com. Software that people make up templates for that do whatever (take in information) and give you code.
Mostly Ive seen this used for databases. It works with about 8 databased. Ive used it with SQL Server & Access. Regretably, XML & data schema dont fit this criteria.
So basically you import this .dll into your project, run the MyGeneration software and choose what is called "dOOdad" and then work your way through to choosing your database and then choose VB.Net or C#. The MyGeneration Software reads the database and creates classes that duplicate each view & table as a class. It ends up becomming a Typed replication of the data source.
For detailed description of how the code works in reality, check this page out: http://www.mygenerationsoftware.com/portal/dOOdads/VBNETUsage/tabid/54/Default.aspx
If you need to change your database, you just change it and run MyGeneration on it again, then rebuild your datatier (if you have it as a seperate project like I do).
Currently the only part I dont like is that everything is currently code based. There is a new version being worked on in which the classes all show up in a visual manor and as a datasource for visually setting datasources & fields.
Right now you can do all of this via code.
Its far and away easier than the 3 weeks I spent comming up with a datateir on this app 2 years back... which had like 1/100th the functionality this datatier has. But Im still not sure if this is better than ADO.Net 2.0 and VS2005 database assisting.
Im going to be working on this for a project Ive not felt like working on because of my database annoyances. At work right now were still working with a dataset and were at the very first steps to converting a really huge database app from another database. This sort of datatier would sure be quick to get data up and working and might be more comfortable for some of the developers who are more used to programming code flat out written for database manipulation.
Anyone have any input on this?
In 2005, it seems Microsoft takes care of that for you. You create a datasource of your database and Visual Studio creates a perfect replica of the database as a dataset and creates a tableadaptor (custom class) for each table. Sounds great and seems to work well.
This weekend I was stumbling around online for development tools and came across www.mygenerationsoftware.com. Software that people make up templates for that do whatever (take in information) and give you code.
Mostly Ive seen this used for databases. It works with about 8 databased. Ive used it with SQL Server & Access. Regretably, XML & data schema dont fit this criteria.
So basically you import this .dll into your project, run the MyGeneration software and choose what is called "dOOdad" and then work your way through to choosing your database and then choose VB.Net or C#. The MyGeneration Software reads the database and creates classes that duplicate each view & table as a class. It ends up becomming a Typed replication of the data source.
For detailed description of how the code works in reality, check this page out: http://www.mygenerationsoftware.com/portal/dOOdads/VBNETUsage/tabid/54/Default.aspx
If you need to change your database, you just change it and run MyGeneration on it again, then rebuild your datatier (if you have it as a seperate project like I do).
Currently the only part I dont like is that everything is currently code based. There is a new version being worked on in which the classes all show up in a visual manor and as a datasource for visually setting datasources & fields.
Right now you can do all of this via code.
Its far and away easier than the 3 weeks I spent comming up with a datateir on this app 2 years back... which had like 1/100th the functionality this datatier has. But Im still not sure if this is better than ADO.Net 2.0 and VS2005 database assisting.
Im going to be working on this for a project Ive not felt like working on because of my database annoyances. At work right now were still working with a dataset and were at the very first steps to converting a really huge database app from another database. This sort of datatier would sure be quick to get data up and working and might be more comfortable for some of the developers who are more used to programming code flat out written for database manipulation.
Anyone have any input on this?