Hi,

You can see a screen-shot here. It basically was built as a sample project that offers an alternative DNN site management that is dedicated for massive updating and a general view that lets you see all the DNN site definitions from a robust AJAX based application.

The reason that we did not use Visual WebGui as our site platform is that it was not built for this purpose. Visual WebGui is dedicated for creating applications rather then sites. We consider ASP.NET and JSP a generic tool that provides lots of work for developers aiming on creating rich client web applications which are often considered to be enterprise applications such as the outlook web access and many other applications. Non enterprise developers also are faced with the need to create admin applications or to embedded small application behaviors with in a large ASP.NET site. For example we have developers that had replaced the DNN image gallery with a VWG based version. Any way we believe that developing these kind of application should not settle for a generic web application environment such as ASP.NET or JSP, which leaves them with lots of work building a framework over those environments.

That is also why we enable tight interaction with ASP.NET by hosting VWG applications with in ASP.NET sites or embedding ASP.NET resources with in a VWG form. This concept is based on using the right tool for the right task. Building sites like our site using VWG does not give any advantage as the developer is faced with application terminology which is based on the WinForms model.

Hope I managed to clear this issue.

Sincerely,
Guy