Navigation, find usages, file structure for F# scripts in Rider 2018.1 EAP!
Our latest EAP builds of Rider 2018.1 come with a number of F# scripting updates, such as several bugfixes related to Mono, and no longer requiring MSBuild 12 to be installed. We are also bringing more ReSharper features to the world of
.fsx files: navigation in scripts, find usages and support for the file structure view. We also added code completion and navigation for
#load directives. Let’s check these out!
Navigation, find usages, file structure
Rider now supports more ReSharper features for scripts, such as navigation to symbols defined in scripts. For example, when using Search Everywhere (Ctrl+T in the Visual Studio keymap), we can see functions (and other members) from our
.fsx file are now available:
When a script is opened in the editor, we can navigate to classes, functions, variables, and other members using Go to File Member (Alt+\):
Speaking of file members: the File Structure tool window (View | Tool Windows | Structure or Ctrl+Alt+7) displays the structure of the script in the active editor tab. The File Structure view and editor tab are synchronized. We can navigate through our script using the mouse, or by typing a few characters and using the arrow keys.
Find usages (Shift+F12) and other navigation features (Alt+`) now work as well, allowing us to figure out where certain symbols are used in our script file (or referencing script files):
Code completion and navigation for
Scripts often use the
#load directives to reference assemblies or include other script files. Rider 2018.1 brings smart completion for paths in these directives. We can use regular completion and traverse the complete tree, but using Smart Completion (Ctrl+Alt+Space), Rider will suggest applicable files from subdirectories:
Features like code completion and find usages work across scripts and project. When compiling the project and referencing its output assembly in a script, we can
#r reference the assembly and get code completion for types from that assembly. What’s more: we can navigate to the type declaration, and from there find usages, mapping back to our script!
We can navigate to included files using Ctrl+click or Navigate to Declaration (F12).
Similarly, referenced assemblies are loaded in ReSharper’s index, making their symbols and members available for search and navigation, including navigation to decompiled sources using Rider’s built-in decompiler.
We’d love to hear your feedback on these updated features! Give the latest Rider 2018.1 EAP build a try!
Subscribe to Blog updates
Thanks, we've got you!
Visualize Entity Framework Relationships and Additional Query Analysis in ReSharper 2023.3
A lot of teams are using Entity Framework or EF Core to work with their database. As an Object-Relational Mapper (ORM), it bridges objects in code to a relational database model, so that as a developer you don’t have to worry too much about the actual database. We all know: that’s not entirely tr…
Automatically Analyze ASP.NET Core Performance With Dynamic Program Analysis
Slow web pages may make your users or customers abandon your web application, even before they’ve had a proper look at it. You’ve likely also been frustrated working with a web application that is slow to load. The good news is that the latest versions of ReSharper and JetBrains Rider’s Dynamic P…
OSS Power-Ups: MassTransit – Webinar Recording
The recording of our webinar, OSS Power-Ups: MassTransit, with Chris Patterson, is available. This was the thirteenth episode of our OSS Power-Ups series, where we put a spotlight on open-source .NET projects. Subscribe to our community newsletter to receive notifications about future webinars.…
Eager, Lazy and Explicit Loading with Entity Framework Core
Entity Framework Core (EF Core) supports a number of ways to load related data. There’s eager loading, lazy loading, and explicit loading. Each of these approaches have their own advantages and drawbacks. In this post, let’s have a quick look at each of these ways to load data for navigational prope…