![]() ![]() One of the biggest annoyances when working with C# and F# projects that interoperate in the same codebase is that you need to rebuild projects to see updates in other projects if they cross the C# F# boundary. Better mixing of C# and F# projects in your solution This allows colorization, tooltips, and further navigation to work exactly as if they had been declared as signature files in your own codebase. When you navigate, Visual Studio generates a complete F# Signature File that represents the module or namespace that the symbol lives under, with XML documentation if it is present. Now it’s here!Īs shown in the video, you can either use the f12 key or ctrl+click to navigate to a declaration, just like in source code in your own solution. We’ve had a feature request since 2016 and several trial implementations throughout the years. Let’s dive in! Go to Definition on external symbols More tooling performance and responsiveness improvements.Better support for mixing C# and F# projects in a solution.Support for Go to Definition on external symbols.For this release, we’re continuing our trend of improving the F# experience in Visual Studio to build upon what was released in the VS 16.9 update last February. We’re excited to announce updates to the F# tools for Visual Studio 16.10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |