3 Answers, 1 is accepted
Currently, JustCode does not have F# support. For now we don't have any specific plans if or when we are going to implement it. If we get more requests about it and we see that more people would benefit from it we will consider it.
Kind regards,
Ivo Bratoev
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>
Rank 1
When I refer to F# assemblies from my C# code, JustCode puts a red squiggle under any types defined in the F# assemblies, and states "Unknown type or namespace". And any property defined to be of the type defined in the F# assembly complains "Unknown member."
However, the code compiles and runs flawlessly. Intellisense continues to work flawlessly on the "unknown" types.
Even if JustCode never gets full-fledged F# support, it seems that it should be able to resolve types defined in F# assemblies, considering that Visual Studio itself is doing it just fine.
We use F# in many of our projects, and having JustCode report bogus problems really diminishes the value of JustCode for my team. Thank you for looking into this!
Thank you for the feedback and sorry for the inconvenience!
As you already know, JustCode doesn't support F# project, thus it is impossible to it to resolve types declared in F# source code. Currently, our team is focused on rebuilding JustCode for VisualStudio 2015 using Roslyn API (we have already released several vesions of it, you can give it a try) and that's why I can't commit that this issue will be resolved any time soon. Also, because of we are using Roslyn to parse the syntax and provide us with the necessary semantic information, there will be no more Good-Code-Reds/Yellows, hence there will be no more false-errors when you reference F# projects, too.
I could suggest you to refer not the F# projects but the their output assemblies instead, while you are working on C#. This way our analyzer will be able to obtain type information from IL, and when you are done roll back the references to the projects. I understand this is pretty inconvenient and annoying but it's the only workaround I can offer you right now.
Once again, excuse us for the caused inconvenience!
Best Regards,
Nikolay Valchev
Telerik