These are chat archives for Microsoft/visualfsharp

20th
Mar 2017
Tuomas Hietanen
@Thorium
Mar 20 2017 09:54
Is there a blog article how to set VS2015 to use those?
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'fsc, Version=4.4.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed.
Hosch250
@Hosch250
Mar 20 2017 15:41
I think you need to use a binding redirect.
Redirect the 4.4.0.0 to 4.4.1.0. That solved that problem for me, anyway.
Victor Peter Rouven Müller
@realvictorprm
Mar 20 2017 16:24
Hey fellow developers. I would like to contribute to the tooling. I thought asking here where I could start would be a good idea.
Victor Peter Rouven Müller
@realvictorprm
Mar 20 2017 16:34
I think I'll paste some complains a person made on the F# slack team in general
Victor Peter Rouven Müller
@realvictorprm
Mar 20 2017 16:41

examples of issues I've faced just yesterday:

1 - I can't navigate between C# and F# code using "go to definition" they don't understand each other

2 - I can't organize the code in a way I'd like to because F# projects don't support folders very well

3 - I can't explore third party APIs the way I'm used to (maybe I should be trying another workflow?) because Intellisense doesn't really work in F#, at least not in the way it does in C# with Resharper. For example I can't simply instantiate a class and set its properties the way I would in C# because I don't really know what properties are there and intellisense doesn't pop up

4 - I have to consume a third party SOAP service written by some idiots in java, and it has custom namespaces for some parts of the XML, and I couldn't find a way to customize the SOAP type provider to match those definitions so I had to fallback to a C# project and customizing the generated code in there
Yemi Bedu @ P&R
@pr-yemibedu
Mar 20 2017 16:57
for (2) i would say looking at http://fsharpforfunandprofit.com/posts/recipe-part3/ programming F# is actually not optional in F#
Victor Peter Rouven Müller
@realvictorprm
Mar 20 2017 16:58
I told the person so too
That some things are different
@pr-yemibedu do you know where I should start for getting into VS F# tooling?
Yemi Bedu @ P&R
@pr-yemibedu
Mar 20 2017 17:00
they should watch this http://www.youtube.com/watch?v=WI9bNWzTkxs it explains why they may not want to use F# but what they should be willing to think about if they do.
i have to find some gitter people to complain to, this link preview is way too large.
Yemi Bedu @ P&R
@pr-yemibedu
Mar 20 2017 17:14
for (1) now that F# is living on Roslyn (at least parts of it), this ability should hoping be already in the works from 2017 and onwards.
please look at https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-f-4-1-and-the-visual-f-tools-for-visual-studio-2017-2/ for what has already been done. Obviously look at https://github.com/Microsoft/visualfsharp/issues and find what interests you or you are good at. Also a particular issue already exists that you may want to try and tackle Microsoft/visualfsharp#2539 for problem number (2).
Victor Peter Rouven Müller
@realvictorprm
Mar 20 2017 17:20
@pr-yemibedu thanks for this info =)
Yemi Bedu @ P&R
@pr-yemibedu
Mar 20 2017 17:26
i have do not have very useful input for (3) and (4). Sorry. The Resharper team may have input for (3) and (4) seems like an edge case of the general use of the type provider. definitely have them put in some issue tickets to expand the feature sets in these useful ways. there are likely thousands to millions of eyes watching.