.NET databinding - who uses it?

[WannaFly]

I thought .NET databinding was the best thing ever when I was using it on small, non complex forms. I'm working on this current form, has about 35 fields on it, textboxes,checkboxes, datetime, etc and its a pain in the ass. I just smiply cannot seem to get it working - i'm always getting an error on the currencymanager or the data doesnt update, etc. I'm about to give up, but I need to get this done

So has anyone else used .NET databinding, what do you think of it? If there are any gurus that are up for helping me, speak up

 

[Kntx]

I've been working on a .net project for about 4 months now and use it all the time. I was new to .net when I started, and had my frustrations with DataBindings but once I got past the issues I think it's great!

ps. Usually I bind to business objects and not directly to the database. So I've never had to deal with concurency issues caused by DataBindings.

 

[UCJefe]

I use it heavily. If you're having a specific problem, post it and we'll help you out.

 

[WannaFly]

UC, Thanks i've FINALLY figured it out, it was a stupid error on my behalf. I've used databinding a lot, just only with a few text fields. Thanks.

 

[DJFuji]

really quick kind of related question-- those of you who work in enterprise .NET applications-- do you use the 3-tier "presentation, business. data" layers to interact with data? I've been using that model for a few years now but just wondering how everyone else has been doing it. It's kind of a pain in the ass to get data to go through all 3 tiers sometimes but it helps to modularize things.

 

[UCJefe]

Originally posted by: DJFuji
really quick kind of related question-- those of you who work in enterprise .NET applications-- do you use the 3-tier "presentation, business. data" layers to interact with data? I've been using that model for a few years now but just wondering how everyone else has been doing it. It's kind of a pain in the ass to get data to go through all 3 tiers sometimes but it helps to modularize things.

Always! The minute you start having SQL queries mixed with UI code or business logic in a button click event handler or something you're asking for trouble. Plus the layers spread out nicely onto backend web services, etc. That way, different UI elements (ex. smart client + ASP.NET page) can share all of the same business logic without duplicate code. There are a bazillion other reasons but the short answer is that yes, separation of layers is very important in enterprise level coding with any technology.

 

[WannaFly]

Originally posted by: DJFuji
really quick kind of related question-- those of you who work in enterprise .NET applications-- do you use the 3-tier "presentation, business. data" layers to interact with data? I've been using that model for a few years now but just wondering how everyone else has been doing it. It's kind of a pain in the ass to get data to go through all 3 tiers sometimes but it helps to modularize things.

I'll agree with Jeff - yes. I have a friend that doesn't/didn't on a recent project, i've shown him mine and it will take him forever to separate it, if he even can, because the project is so close to being done.

 

[XZeroII]

Originally posted by: DJFuji
really quick kind of related question-- those of you who work in enterprise .NET applications-- do you use the 3-tier "presentation, business. data" layers to interact with data? I've been using that model for a few years now but just wondering how everyone else has been doing it. It's kind of a pain in the ass to get data to go through all 3 tiers sometimes but it helps to modularize things.

I just learned about it about a year ago and it was a revelation to me. I can't stand looking at stuff I did before. Design patterns should be a required first semester class in college. If you don't know 'em, you don't know anything.