Visual WebGui is actually based on the core objects of ASP.NET but implementing a different pipe line. This means that a Visual WebGui application project is actually an extended ASP.NET application project to support the new pipe line. ASP.NET entities can be created the same way they are created on a regular ASP.NET application project. This also means that the Visual WebGui entities and the ASP.NET entities are sharing the same application context.
When you use the Visual WebGui Context.Session object you are actually refereeing an object that is hosted with in the ASP.NET session object and the same applies to the Context.Application which is actually an object hosted with in the ASP.NET application object. You can easily refer to the original ASP.NET objects by using the HttpContext.Current.Session or HttpContext.Current.Application but by referring directly to those object you loose the ability to also deploy a Visual WebGui as a client application which is a feature that we are currently working on.
This actually means that you can use for example the gateway concept to embed an ASPX page with in a Visual WebGui application. This is an excellent way to embed an existing ASP.NET control but this is a subject for another post. You can also use a Visual WebGui entity from an ASP.NET entity by using the adapters concepts but that is to for another post. I will soon cover both these issues and supply sample apps using these concepts.