Back to Questions
1.8k
views6
comments
Compiler error after VS upgrade to 15.7.0
websharpercompilerq&a

This is more of a quick question... Have you noticed FSC compiler error below when upgrading to Visual Studio 15.7.0 ?

With the latest WebSharper 4.2.10 when several developers upgraded VS we all saw the problem below. There are a number of F# improvements in the 15.7.0 release, see: https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#fsharp

It seems the compiler is failing to parse a string as an integer. We think it's a new "--nowarn: NU1603" compiler argument which was not present prior to the VS upgrade. Is it possible the wsfsc compiler is not coping with this ?

Anyway, before we strip this down and test the samples etc... I thought to pose the question early. It's certainly possible the problem is on our side.

FSC : WebSharper error FS9001: Global error 'Input string was not in a correct format.' at at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at Microsoft.FSharp.Core.LanguagePrimitives.ParseInt32(String s) at Microsoft.FSharp.Collections.Internal.IEnumerator.map@74.DoMoveNext(b& ) at Microsoft.FSharp.Collections.Internal.IEnumerator.MapEnumerator1.System-Collections-IEnumerator-MoveNext() at Microsoft.FSharp.Collections.SetTreeModule.mkFromEnumerator[a](IComparer1 comparer, SetTree1 acc, IEnumerator1 e) at Microsoft.FSharp.Collections.SetTreeModule.ofSeqa at WebSharper.FSharp.Program.parseIntSet@298(String s) at WebSharper.FSharp.Program.compileMain$cont@276(String argv, Unit unitVar) at WebSharper.FSharp.Program.main(String argv)

.

Hi! The fix for nowarn is now released in https://github.com/dotnet-websharper/core/releases/tag/4.2.11.258

By on 5/17/2018 8:16 AM ()

Thanks very much András.

By on 5/17/2018 8:23 AM ()

It seems this is related to NuGet messing with compiler options and adding the "--nowarn: NU1603" in our case. However, the (MS) F# compiler was recently upgraded to cope with alphanumeric arguments, see: https://github.com/Microsoft/visualfsharp/issues/3626

Please can the WebSharper compiler be fixed to follow suit?

By on 5/8/2018 4:42 AM ()

Indeed, this should be fairly quick to fix. We'll publish a hotfix ASAP.

By on 5/9/2018 1:56 AM ()

Thanks very much, Loïc. Rob

By on 5/9/2018 1:57 AM ()

You can track the issue here: https://github.com/dotnet-websharper/core/issues/945

By on 5/9/2018 2:27 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