Kevin Ransom

@smoothdeveloper --- we would continue to ship a desktop compiler - though it would not be installed by default, however, it would be a frozen in time compiler at F#...

The dotnet sdk is unlikely to ever allow loading legacy desktop framework assemblies. So if there are type providers that have not migrated at least to netstandard2.0 we should work...

@abelbraaksma It's not really a language thing, it's more a product thing so I think we can handle it here. The only authorized way to get fsc.exe and fsi.exe these...

@abelbraaksma to be honest about moving on ... the compatibility with existing projects is terrifying. We believe we can still build Silverlight apps, even though we haven't even tested it...

@baronfel , @vzarytovskii --- so are you suggesting that what we do now is correct? or perhaps that the actual final implementation requires a more rigourous analysis than is currently...


Okay, the current Fsi behaviour is this, if you start with send to interactive, it uses a global.son when present in the same directory as the script to figure out...

@smoothdeveloper The parser knows nothing about any specific directives, except for __SOURCE_DIRECTORY__ | __SOURCE_LINE__| __SOURCE_FILE__. I had no intent to teach the parser about the specific directives, although that may...

@brianrourkeboll, we could and perhaps should pass the Nuget nowarns through to the nuget package manager. We currently don't.

@Tangent-90 - Hey, I was wondering why would an internal abstract member not be allowed on a public type? After all the assembly where it is defined, as well as...