Back to Questions
1.2k
views5
comments
WebSharper site to Azure returns "This web app has been successfully created" splash screen
websharperdeploymentazure

For a first Azure deployment test, I created a UI.Next Client-Server Application from the template, compiled and verified that it runs locally. And then I deployed to Azure using Visual Studio's Publish wizard. It took a couple of tries before the publishing succeeded. But now that it's successfully deployed, the site still displays the default Azure "This web app has been successfully created" splash screen. I verified that the bits are deployed using the Kudo debug console.

Is there something else that must be done?

Thanks!

.

I was able to get past the splash screen by fetching the latest nuget packages. But now I'm getting Could not load ... FSharp.Core error. So far I haven't figured out how to resolve this issue. The binding redirects in web.config seem correct.

Could not load file or assembly 'FSharp.Core, Version=4.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

By on 9/14/2015 3:29 PM ()

I was able to work around this second issue by closing the project in Visual Studio 2015 and opening it in VS 2013. In VS 2013, I then set the Target F# runtime to 4.3.1.0 and after deploying again to Azure the site ran without raising exceptions.

However, if I open the project again in Visual Studio 2015, the Target F# runtime box is empty and F# 3.1 is not listed as an option. Leaving the runtime combo empty or selecting F# 3.0 both produce the Could not load file or assembly 'FSharp.Core ... exception when deployed to Azure. So at this point I'm not able to use VS 2015 for deployment.

By on 9/14/2015 4:04 PM ()

Got a repeatable process for publishing a new public/anonymous access UI.Next site to Azure using Visual Studio 2015.

1. Create new WebSharper project using UI.Next Client Server Application template.
2. On Project Properties' Application tab, set:
Target Framework: .NET Framework 4.5
Target F# runtime: F# 3.1 (FSharp.Core, 4.3.1.0)
3. In app.config, increase FSharp.Core binding redirect's upper version from 4.3.1.0 to 4.4.0.0. E.g.,
<bindingRedirect oldVersion="0.0.0.0-4.4.0.0" newVersion="4.3.1.0"/>
4. Publish twice
1st time: immediately throws an exception
2nd time: publishes and site works

Note: Updating Nuget packages wasn't necessary; template works as-is.

By on 9/14/2015 5:01 PM ()

Awesome that you got it working, thanks! Any idea why the need to publish twice? (I can confirm this is indeed the case.)

By on 9/16/2015 5:29 AM ()

No, I'm not sure why a second publish is required.

By on 9/21/2015 11:42 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper