add simple project classifier authoring for .fsproj#1681
add simple project classifier authoring for .fsproj#1681KevinRansom merged 1 commit intodotnet:masterfrom brettfo:project-classifier
Conversation
KevinRansom
left a comment
There was a problem hiding this comment.
Wow ... that's all you need to get project detection and auto install ... that is pretty groovy.
|
Interesting. I get expected behavior when opening some F# project on preview 5 today already, but hadn't tested attempting to open a project authored in VS "15". |
|
What about fsx files outside of projects like we have in many scenarios (especially FAKE). Is this addressed as well? |
|
@forki Not sure if it's possible to have breadcrumbs (that's the name) for specific files - thus far it's just been project-level classification. I'd like file-level classification too - I'll ask some folks. Just to clarify, the scenario is this: Someone opens an F# script file in Visual Studio, and they do not have F# tools installed. Opening that script file in VS prompts them to install the F# tools. |
|
re breadcrumbs for fsx: I think it would be worth it to include something like this (#1040 (comment)) also for fsx files. |
|
@cartermp yes exactly. We had this feature request since ms removed F# from default installation. |
|
@cartermp and thanks for taking care of this. It always was a super important use case for many C# users that used F# only for FAKE. Side note: "Fixes internal bug 271787" - sad to still see such things here. (yeah I know why). |
This will enable newer installs of VS to prompt you to install the F# tools when attempting to open a .fsproj.
@KevinRansom @OmarTawfik
Fixes internal bug 271787.