All views that use the master template should @inherit from UmbracoTemplatePage. UmbracoTemplatePage actually inherits from Umbraco.Web.Mvc.UmbracoViewPage and has two additional properties CurrentPage and Umbraco, the latter as you say is an instance of the UmbracoHelper class.

I'm fairly sure that you cannot replace this with a custom model because an instance of model is determined by the Umbraco routing. However, if you wish the views to have a custom model you should child actions instead. These will allow you pass you custom objects into the page independently of the RenderModel.

If you want something to be available throughout all pages/views regardless of whether they are views, partial views or child actions you could create a global filter that sets data to the Viewbag from the session for example. Visualarq Crack on this page. Hdd Regenerator V2011 Crack Programs here. There is some documentation here which may help talk you through.

There are 2 types of templating technologies in Umbraco: MVC (views) WebForms (masterpages) By default Umbraco uses MVC templates. Working with MVC (views, razor, etc. Install Ragged2e Package there. Working with MVC in Umbraco. How to work with MVC templates in Umbraco. Working with MVC Views and Razor syntax in Umbraco. See some quick examples here.