Add New Item to Visual F# project has an incorrect tree structure

[KevinRansom]

Decription:
When adding an item to an F# project the Item selector displays an incorrect tree structure Picture below.

The tree is:
Visual F# Items
Code
Visual F# Items
Code
Data
General

Clearly the first Visual F# Items and code are incorrect.

Repro:

1. Start VS2015
2. Add new F# Library Project
3. In solution explorer window select Add new item

Note: I am confident the fix will not be in the open part of the codebase, reporting here to avoid dupes.

Twitter: @codecutterman

[latkin]

I do not repro using an internal VS drop from last week, or with VS 2015 preview. Does anyone else see this?

[latkin]

Does not repro for me with fresh install of VS 2015 CTP6 + latest F# package.

Per our hallway convo - I wonder if this is due to EnableOpenSource installation/development on your box? Maybe a tree path got horked while you were debugging that guy.

[KevinRansom]

I agree it was likely a configuration issue

[bentayloruk]

I have just had the same issue with VS 2015 RC. It is wrong in 2015 RC and correct in 2013. As the following images demonstrate. Is there anything I can do to help figure this out, or is it likely I've done something rogue! 😄

VS 2015 RC

VS 2013

[PatrickMcDonald]

Here's what my 2013 dialog looks like if that helps (So just the extra Code node from Kevin's screenshot is different):

I think the Extensibility node is from SideWaffle, and the Web node is from dmohl's addon

[isaacabraham]

Bizarre, I just checked and have the same SQL stuff showing in the Visual F# Items bit (if you drill down, it's located in Data).

I did upgrade from CTP4 or 5 to the RC - maybe this is something left over from then.

[latkin]

Yeah I am actually seeing this now, too, after installing RC.

[latkin]

This bug just won't go away...

Right now, F# "new item" dialog looks correct with the default set of extensions that come with VS. However there appears to be some VS platform issue (or maybe setup bug on our side) whereby installing/uninstalling other extensions can cause our root node to disappear.

I have confirmation from our team and the VS platform team that it's too late to make further changes for this, so we will live with it for now. I have a lead on a proper fix, will look at that for vNext.