Home/ Questions/Q 3426440
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T06:42:58+00:00

I am currently reading the book Pro WPF in C# 2008 , and I’m

  • 0

I am currently reading the book Pro WPF in C# 2008, and I’m a newbie to WPF.

I basically have a questions regarding best practice, as I want to write code that is commonly accepted by other developers.

I see throughout the book, that the author uses different ways of closing tags for different purposes. I’ll give an example:

When creating a grid, and defining the rows and columns, he always write this code similar to this:

<Grid.ColumnDefinitions>
  <ColumnDefinition />
  <ColumnDefinition />
</Grid.ColumnDefinitions>

So he closes the tag “inline” inside the tag since the tag does not have any content (I’m not sure if inline is the correct wording for this)

But most other places, he will put a closing tag, even if it’s no content like this

<TextBlock Text="{Binding Path=CategoryName}"></TextBlock>

I also see, that if he defines any attributes in the ColumnDefinition case he will also add the closing tag like this

<ColumnDefinition Width="Auto"></ColumnDefinition>

My question is simply. Are there any reason to write it like this? I think it looks more tidy to omit the closing tag is there is no contents in all cases.

So is this just a matter of personal preference, or are there any other reasons to switch between the two.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is more of an XML thing than a WPF thing and mostly doesn’t matter since they just parse the XML. In general though I’d recommend always to use “Empty elements” (<tag/>) when you don’t have any child elements since it both looks cleaner and prevents any accidental whitespace in the contents of the tag.

    He’s probably just inconsistent in the book by accident

    • 0