Why do a lot of ASP.NET CMSs use individual pages, rather than one page with parameters?
<p>I've noticed a trend in blogs, online newspapers written in ASP.NET, where rather than having one page serve content (something like <code>/Article.aspx?ID=foo-bar</code>), a new (physical) page serves one article (eg <code>/Articles/Foo-bar.aspx</code>). It looks unnecessarily complicated, especially if an article was deleted/edited, and kind of defeats the purpose of a dynamic CMS. Also, if "pretty URLs" were desired, they could just be rewritten using the IIS URL rewriter.</p>

<p>Is this some sort of convention used in ASP.NET?</p>

<p><strong>Edit:</strong> Here are some example URLs I've seen:</p>

<p><a href="http://www.itnews.com.au/News/322888,nab-splits-cio-role-in-two.aspx" rel="nofollow">http://www.itnews.com.au/News/322888,nab-splits-cio-role-in-two.aspx</a>
http://www.thedailywtf.com/Articles/Classic-WTF-The-Abstract-Candidate.aspx</p>
