Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I do a lot of cross-language development where F# code consumes C# libraries. Lack of ability to F12 to go to definition is THE major annoyance in VS2010. I did not notice anything about this on the What’s New page, but then it could be a tooling issue, not necessarily a language issue. Same question for Shift-F12, find all references.
Please help me to make a decision to upgrade (or not).
I’ve just installed VS 11 and made a solution with an F# executable and a C# dll. The F# code calls the a function in the C# code, and the debugger traces into the C# code just as it should, but the result of pressing F12 is still only “Cannot navigate to definition. Source code is not available.“.
BTW, the new look makes it very hard to distinguish tabs, property panes, toolbars etc from the grey background. It all just looks like grey on grey, like something dreamed up in the former Republic of East Germany.