Deploying un-compiled ASP.NET MVC Razor application

Razor views are compiled at runtime, so you always deploy them un-compiled.

What you want is simply Razor pages, so can add them to any directory (not Views) and access them without the file extension (e.g. /Foo/Bar instead of /Foo/Bar.vbhtml).

I don't think I would recommend using the filesystem for this. I think you should save the razor code to the database and then, when you wish to parse it, you may do so according to this Using RazorEngine to parse Razor templates concurrently

Here is another example:

var model = new { Name = "Test" };
var template = "Hello @Model.Name";

var result = Razor.Parse(template, model);

Code taken from Using Razor engine on strings - not views

Edit to answer your questions:

The razor code would be stored in the database along with whatever controller you wanted to run it. When you retrieve the razor code from the database, you would also know the controller, then you could redirect to that controller, sending whatever model you want, to the razor code, and then parse it as shown above. Make sense?

The routing configuration can be customized to identify a URL pattern that identifies all requests for customized code and route them through a common controller that can then load arbitrary views based on information provided in the URL. Notice the route with the name Custom below, and how it always uses the Index action of a controller named Custom, but introduces a new parameter customization.

Public Class RouteConfig
   Public Shared Sub RegisterRoutes(ByVal routes As RouteCollection)
      routes.IgnoreRoute("{resource}.axd/{*pathInfo}")

      routes.MapRoute( _
         name:="Custom", _
         url:="custom/{customization}/{id}", _
         defaults:=New With {.controller = "Custom", .action = "Index", .id = UrlParameter.Optional} _
      )

      routes.MapRoute( _
            name:="Default", _
            url:="{controller}/{action}/{id}", _
            defaults:=New With {.controller = "Home", .action = "Index", .id = UrlParameter.Optional} _
        )
   End Sub
End Class

Once this is set up, add a controller called CustomController to the project that simply passes through to a view determined by the customization parameter:

Public Class CustomController
   Inherits System.Web.Mvc.Controller

   '
   ' GET: /Custom

   Function Index(customization As String) As ActionResult
      Return View(customization)
   End Function

End Class

Publish this code and add a Custom directory under the Views directory in the deployed location. Now you can put any .vbhtml file in the Custom folder and refer to it with a URL like http://localhost/MyApplication/Custom/MyView, which will load MyView.vbhtml from the Views\Custom directory.