That is precisely my point from the very beginning. And it really is silly to say that "ASCX skins are not controls" because by Microsoft definition of Microsoft technology standards anything that is *.ascx is by very definition a control in contrast to *.aspx page. So it is "just flat out wrong" for you to claim that I am "just flat out wrong".
I have said over and over again exactly what my concern is and exactly what my request for an enhancement/improvement is. I regret that you, Jeff, fail to understand.
I have repeatedly expressed my objection to and dissatisfaction with the fact that it is not possible to view/preview the skin outside of a "dynamic DNN site" with a dynamic Default.aspx page to drive and load the skin. That was the entire point of my discussion of crafting a separate mockup DefaultDesign.aspx page to drive view/preview/development of the skin inside the VS2008 environment without requiring a live dynamic DNN site.
There is absolutely nothing wrong with either my understanding or my suggestions/requests for any kind of enhancement I may be interested in. Just as the Core Team has every right to ignore any request or suggestion I make, I also have every right to maintain my opinion that it should be possible to quickly and efficiently design a skin without the burden of the entire live dynamic DNN installation - ie, using a static template with mockup text placeholders for the key DNN objects while at the same time using VS2008 and any other *.ascx controls under development by the developer.
Jeff, you need to slow down, read posts more carefully, and be much more circumspect, prudent, and respectful before you start accusing anybody of being "just flat out wrong".
Frankly, I'm beginning to wonder whether I should continue to post to these forums given the nature of some of the responses which leave me wondering whether I should ignore them or respond to them.