However, here’s the catch. I generally advise against delving too heavily into seperating out presentation logic unless you have a need to have more than one view.

But, with that being said, the trick is to delegate everything to your presentation logic from the UI. So, in your case, you might have an object like PropertyListing, which is a list of the homes the user selected. And then a PropertyListingPresenter which handles interacting between the business object and your UI code through an interface. That interface might look like:

public interface IPropertyListingView
{
void SetPropertyListing(PropertyListing);
void PropertySelected(Property);
}

and your view implement it like:

protected void SetPropertyListing(
  PropertyListing listings)
{
  this.PropertyListDataGrid.DataSource = listings;
  this.PropertyListDataGrid.DataBind();
}

protected void PropertyListDataGrid_ItemSelected(object sender, EventArgs e)
{
  PropertySelected((Property)e);
}

So, again, you are just delegating everything to the Presenter class.

Does this help?

The problem is actually handling the UI display logic.
For instance, I’ve a remove button that should be enabled only when I’ve selected an item on a list.
What controls this behavior?