data bound controls?

[mapperkids]

Hi,

In Vb6, most experts suggest not to use the data bound controls, how about in vb.net? does the same theroy apply too, or MS make the better job in VB.net?

Thanks

[jmcilhinney]

.NET data-binding is completely different to VB6 data-binding. Data-binding in .NET apps is a very good idea. It reduces the amount of code you have to write, sometimes by an enormous amount, and reduces the likelihood of errors. Data-binding in .NET 2.0 is also improved over .NET 1.x. Like anything, the more you understand the data-binding mechanism the better you will be able to use it and the more you will be able to diagnose issues with your code that uses it. Also, data-binding is not appropriate in all situations, so the better your understanding of how it works the better you will be able to distinguish the situations in which it is not appropriate.

[mapperkids]

.NET data-binding is completely different to VB6 data-binding. Data-binding in .NET apps is a very good idea. It reduces the amount of code you have to write, sometimes by an enormous amount, and reduces the likelihood of errors. Data-binding in .NET 2.0 is also improved over .NET 1.x. Like anything, the more you understand the data-binding mechanism the better you will be able to use it and the more you will be able to diagnose issues with your code that uses it. Also, data-binding is not appropriate in all situations, so the better your understanding of how it works the better you will be able to distinguish the situations in which it is not appropriate.

Thanks, I should try to understanding and use the data bound control then. Since the back end is SQL server 2005. Can I convert the vb.net application to ASP.net in the future without too much re-coding.

Thanks!

[jmcilhinney]

Thanks, I should try to understanding and use the data bound control then. Since the back end is SQL server 2005. Can I convert the vb.net application to ASP.net in the future without too much re-coding.

Thanks!

That depends on how you structure it. If you place all the data access code in the presentation layer then no, not really. Web apps and Windows apps use a completely different presentation layer, i.e. UI, so you would need to keep the data access code separate to that. If you place all your data access code in an independent DLL then you can place any inertface you like on top of it. You might want to look into designing distributed or n-tier apps. That's all about keeping things like data access and UI in separate layers, thus you can combine any layers you like in any combination you like, plus you can make changes to one layer without affecting another, as long as the interfaces through which they communicate don't change.