With ASP.Net Web Pages 2.0 the concept of Mobile views was introduced. Normal webforms also got it with the Microsoft.AspNet.FriendlyUrls.
In both cases the idea is that whenever you have a file named MyPage.cshtml or MyPage.aspx, you can create a new set of files called MyPage.Mobile.cshtml or MyPage.Mobile.aspx and ASP.Net will automatically be smart enough to choose the Mobile view when its a mobile device requesting the url.
So without much further introduction i suppose the readers by now has figured out where i'm getting at; this file scheme should be supported by Composite C1 as well for .master, .cshtml, .xslt etc.
If anyone, but my, thinks this would be a great addition please go and upvote it here https://compositec1.codeplex.com/workitem/1711. I'm able implement this myself for MasterPages without altering the Core, which i've already done (https://bitbucket.org/burningice/compositec1contrib/src/94f2e3b5715b0a6b99d10d48a45023903319e489/Rendering.MasterPages/Web/MasterPageModule.cs?at=default#cl-59), but for Functions and Razor/Xml templates this has to be supported by C1 natively.
In both cases the idea is that whenever you have a file named MyPage.cshtml or MyPage.aspx, you can create a new set of files called MyPage.Mobile.cshtml or MyPage.Mobile.aspx and ASP.Net will automatically be smart enough to choose the Mobile view when its a mobile device requesting the url.
So without much further introduction i suppose the readers by now has figured out where i'm getting at; this file scheme should be supported by Composite C1 as well for .master, .cshtml, .xslt etc.
If anyone, but my, thinks this would be a great addition please go and upvote it here https://compositec1.codeplex.com/workitem/1711. I'm able implement this myself for MasterPages without altering the Core, which i've already done (https://bitbucket.org/burningice/compositec1contrib/src/94f2e3b5715b0a6b99d10d48a45023903319e489/Rendering.MasterPages/Web/MasterPageModule.cs?at=default#cl-59), but for Functions and Razor/Xml templates this has to be supported by C1 natively.