|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Alternative to strongly typed datasetsHi
I have traditionally developed winform db apps using typed datasets with bound controls. With progress in ADO.NET am I able to use another technique which is more suitable in the long run? Thanks Regards This one is simple, the datacontext from Linq
Show quoteHide quote "John" <info@nospam.infovis.co.uk> wrote in message news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl... > Hi > > I have traditionally developed winform db apps using typed datasets with > bound controls. With progress in ADO.NET am I able to use another > technique which is more suitable in the long run? > > Thanks > > Regards > > > > IMHO
You always need a strong reference type wether it is a dataset with data tables or a custom entity class HTH Michel Show quoteHide quote "John" <info@nospam.infovis.co.uk> schreef in bericht news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl... > Hi > > I have traditionally developed winform db apps using typed datasets with > bound controls. With progress in ADO.NET am I able to use another > technique which is more suitable in the long run? > > Thanks > > Regards > > > > 1. Which framework are you on? 2.0? 3.5? 1.1?
check here http://sholliday.spaces.live.com/feed.rss find the 5/24/2006 Custom Objects/Collections and Tiered Development blog entry. Read it. Try the code. Then also find the "bird's eye view" MS article listed. LINQ is a different suggestion. Entity Framework. However, I'm still on the fence about whether LINQ (to Sql) should always replace a DAL layer (as defined at my blog entry above) for long term..or high demand applications. I am in favor of LINQ for more basic projects, without high demand on the db. Again, this is one (of many) opinions and I'll still weeding through it. I'm not an expert in LINQ....I'm getting better. I have a 2.0 example (you can find it at the feed.rss url above), but reading through the 1.1 version is a better starting place, because I have strong datasets in that project to compare. I ~always (almost always that is) pick custom business objects over strong datasets. My one exception is reports. I use the push method (and push strong datasets) to report objects. Active Reports and/or Crystal Reports. The reason? Because reports change over time (get "tweaked") the overhead of custom business objects seem too high a price (IMHO, again this is one opinion amongst many). I just prefer to whip up a strong dataset, populate it, and let it be the model (datasource) for the report. ....................... Don't forget about LINQ to Objects. 2 technologies are always mutually exclusive. ................ PS Ludwig C# Generics for a good (2.0 flavor) article on how to work with (sort, search, etc) Custom Business Objects (and their collections). Good luck. Show quoteHide quote "John" <info@nospam.infovis.co.uk> wrote in message news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl... > Hi > > I have traditionally developed winform db apps using typed datasets with > bound controls. With progress in ADO.NET am I able to use another > technique which is more suitable in the long run? > > Thanks > > Regards > > > > vs 2008 fw any upto 3.5
Thanks Regards Show quoteHide quote "sloan" <sl***@ipass.net> wrote in message news:OSyRAUh8JHA.1252@TK2MSFTNGP04.phx.gbl... > > 1. Which framework are you on? 2.0? 3.5? 1.1? > > > check here > http://sholliday.spaces.live.com/feed.rss > find the > 5/24/2006 > Custom Objects/Collections and Tiered Development > blog entry. > Read it. Try the code. > Then also find the "bird's eye view" MS article listed. > > > LINQ is a different suggestion. > Entity Framework. > > > However, I'm still on the fence about whether LINQ (to Sql) should always > replace a DAL layer (as defined at my blog entry above) for long term..or > high demand applications. > I am in favor of LINQ for more basic projects, without high demand on the > db. Again, this is one (of many) opinions and I'll still weeding through > it. > I'm not an expert in LINQ....I'm getting better. > > > > I have a 2.0 example (you can find it at the feed.rss url above), but > reading through the 1.1 version is a better starting place, because I have > strong datasets in that project to compare. > > I ~always (almost always that is) pick custom business objects over strong > datasets. My one exception is reports. I use the push method (and push > strong datasets) to report objects. Active Reports and/or Crystal > Reports. The reason? Because reports change over time (get "tweaked") the > overhead of custom business objects seem too high a price (IMHO, again > this is one opinion amongst many). I just prefer to whip up a strong > dataset, populate it, and let it be the model (datasource) for the report. > > ...................... > > Don't forget about LINQ to Objects. 2 technologies are always mutually > exclusive. > > ............... > > PS > Ludwig C# Generics for a good (2.0 flavor) article on how to work with > (sort, search, etc) Custom Business Objects (and their collections). > > Good luck. > > > > > > "John" <info@nospam.infovis.co.uk> wrote in message > news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl... >> Hi >> >> I have traditionally developed winform db apps using typed datasets with >> bound controls. With progress in ADO.NET am I able to use another >> technique which is more suitable in the long run? >> >> Thanks >> >> Regards >> >> >> >> > > Hi John,
Datasets are here to stay, they won't disappear. But if you want a different approach then you should try an ORM tool: a bundled one (Linq to SQL is good for starting but very limited, EF forthcomming v4 sounds usable) or a commercial one (i.e. my favorite LLBLGenPro). -- Show quoteHide quoteMiha Markic [MVP C#, INETA Country Leader for Slovenia] RightHand .NET consulting & development www.rthand.com Blog: blog.rthand.com "John" <info@nospam.infovis.co.uk> wrote in message news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl... > Hi > > I have traditionally developed winform db apps using typed datasets with > bound controls. With progress in ADO.NET am I able to use another > technique which is more suitable in the long run? > > Thanks > > Regards > > > > "John" <info@nospam.infovis.co.uk> wrote in Technically, the DataSet will be around for quite some time, if that is news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl: > Hi > > I have traditionally developed winform db apps using typed datasets > with bound controls. With progress in ADO.NET am I able to use another > technique which is more suitable in the long run? your reason for bailing. If I were to choose a technology that is up and coming and shows promise, and had to choose from built in stuff, I would choose Entity Framework (EF). -- Show quoteHide quoteGregory A. Beamer MVP; MCP: +I, SE, SD, DBA Twitter: @gbworld Blog: http://gregorybeamer.spaces.live.com ******************************************* | Think outside the box! | ******************************************* Ah, if it's not broken, don't fix it. While the EF might be shiny, new and
appealing, IMHO it does not yet address many serious issues. It also requires you to rearchitect your applications (at least), relearn new skills and forget old ones. -- Show quoteHide quote__________________________________________________________________________ William R. Vaughn President and Founder Beta V Corporation Author, Mentor, Dad, Grandpa Microsoft MVP (425) 556-9205 (Pacific time) Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition) http://betav.com http://betav.com/blog/billva ____________________________________________________________________________________________ "John" <info@nospam.infovis.co.uk> wrote in message news:u3PT9Wa8JHA.1252@TK2MSFTNGP04.phx.gbl... > Hi > > I have traditionally developed winform db apps using typed datasets with > bound controls. With progress in ADO.NET am I able to use another > technique which is more suitable in the long run? > > Thanks > > Regards > > > >  
Other interesting topics
Design Time Controls
static classes are evil ? System.Windows.Forms.Control.Handle==HWND? Uisng ADO.Net The Entity Framework Getting started with a Kiosk-like application Pass Variable At Design Time Read From Application Config File In Class Library Form transparency Win forms designer - controlling the designer code generation What control did Microsoft Use? |
|||||||||||||||||||||||
