Quote Originally Posted by chris128
I agree, I just personally dont see why the UI needs to be separated from the VB code. I mean surely a large percentage of code that we all write is done to update the UI so it makes sense that you need to be able to work with the UI directly from the programming language... After all, for pretty much any windows forms app the whole purpose of it is to show someone data and manipulate that data based on what they click and press, so why try and distance the things that they click and press from the programming logic. Dont get me wrong, I know you can do things like change a label's text or whatever from VB code in a WPF project but the whole "separation" thing just seems unnecessary to me.
I guess it might be good for huge enterprise level business apps but for people like myself it doesnt seem to provide any benefits.
Actually separating the UI from the rest of the program is a design of n-tier.

An example...

UI
Business Rules
Data Layer
Database

So separating the UI from the business rules and even other apps like Fat Clients can have big improvements in many areas if separated.