I have some legacy Webforms code that I need to integrate into my standard Umbraco 7.2 project, with Fanoe starter kit. I've been led to believe (from docs, videos etc) that this was easily achievable by rolling it up into a usercontrol and embedding it as a macro. As I've dived further into it looks like they won't be able to be used with postbacks at all (or can they?). Even ensuring that the usercontrol has a form and scriptmanager doesn't work... it will display fine, but buttons etc. don't do anything.

I can't spend any more time trying to figure it out, can anyone give me a definitive "No it won't work" or "Of course it can, if you do XYZ"?

In the meantime I'm going to create a separate aspx page to hold the control (with appropriate exclusions in web.config), but that does mean running a parallel version of the master template (one as .cshtml, the other as .Master) and trying to convert all my current header & footer partial views to ascx usercontrols. Is there a way to include the razor partial view in my .Master page somehow? If I can't include them then how do I access things like CurrentPage.Site() and recurse through the childpages in the codebehind? The goal being to have the navigation header & footer still coming out of Umbraco, regardless of which template is displaying it.

For instance, how would I replicate this razor partial in aspx? (MainNavigation.cshtml from Fanoe starter kit)

@inherits Umbraco.Web.Mvc.UmbracoTemplatePage
@{ var home = CurrentPage.Site(); }

@if (home.Children.Any())
{
        @* Get the first page in the children *@
        var naviLevel = home.Children.First().Level;

        @* Add in level for a CSS hook *@
        <ul class="level-@naviLevel">            
                @* For each child page under the home node *@
                @foreach (var childPage in home.Children)
                {   
                        if (childPage.Children.Any())
                        {                    
                                <li class="has-child @(childPage.IsAncestorOrSelf(CurrentPage) ? "selected" : null)">
                                @if(childPage.DocumentTypeAlias == "LandingPage") 
                                {
                                                        <span>@childPage.Name</span>
                                    @childPages(childPage.Children)
                                }
                                else
                                {
                                    <a href="@childPage.Url">@childPage.Name</a>
                                }
                                </li>
                        } 
                        else
                        {
                                <li class="@(childPage.IsAncestorOrSelf(CurrentPage) ? "selected" : null)">
                                        <a href="@childPage.Url">@childPage.Name</a>
                                </li>
                        }            
                }
        </ul>
}

@helper childPages(dynamic pages)
{
        @* Ensure that we have a collection of pages *@
        if (pages.Any())
        {
                @* Get the first page in pages and get the level *@
                var naviLevel = pages.First().Level;

                @* Add in level for a CSS hook *@
                <ul class="sublevel level-@(naviLevel)">
                        @foreach (var page in pages)
                        {
                                <li>
                                        <a href="@page.Url">@page.Name</a>

                                        @* if the current page has any children *@
                                        @if (page.Children.Any())
                                        {                        
                                                @* Call our helper to display the children *@
                                                @childPages(page.Children)
                                        }
                                </li>
                        }
                </ul>
        }
}