We\u2019d like to give you a quick update regarding which to-do list items have been completed. As a reminder, most of these new features are available only in Smart Mode.<\/p>\n\n\n\n To download Fleet, please install the\u00a0JetBrains Toolbox App<\/a>. You will see Fleet in the list of available tools.<\/p>\n\n\n\n Let\u2019s start with a vital feature for C# developers \u2013 the Solution View.<\/p>\n\n\n\n If you open a solution ( It shows you the solution structure you\u2019re used to observing in your IDE of choice, including a list of projects in the solution, solution folders, and project dependencies (both NuGet and other projects from the solution), but hiding technical subfolders (like bin<\/em> and obj<\/em> folders).<\/p>\n\n\n\n Now let\u2019s look separately at some additional features inside the Solution View that will simplify your daily .NET routine. <\/p>\n\n\n\n Right from the Solution View, you can now build, rebuild, and clean your solution by calling the context menu for the solution node. For a project node, the Build Project<\/em> action is also available to you.<\/p>\n\n\n\n You can add a new project to a solution by calling the context menu on a solution node in the Solution View. It provides some basic functionality like specifying the name of the new project, providing a project folder to save the project, and setting a type of project with a list of predefined types.<\/p>\n\n\n\n The UI and UX for this new dialog are still under construction and are subject to change.<\/p>\n\n\n\n Fleet can’t determine which solution to open if there are either several If you want to close a particular solution, select the solution in Solution View and call the Close active solution<\/em> action.<\/p>\n\n\n\n Unit testing is also a critical feature, as being able to run and debug your unit tests is essential in the development workflow. We\u2019ve now added Unit Testing functionality for C# to Fleet. Out of the box, Fleet supports the most common unit test frameworks: NUnit<\/em>, MSTests v2<\/em>, and xUnit<\/em>. <\/p>\n\n\n\n You can run unit tests right from Solution View. A new Run Unit Tests<\/em> action is available in the context menu for a solution node, project node, and any C# file. <\/p>\n\n\n\n If you\u2019re used to seeing a green run icon for your unit test methods and classes in the code editor, we\u2019ve got you covered! You can run your tests right from the gutter margin, which can be useful if you want to run only a particular unit test or a set of tests inside a class.<\/p>\n\n\n\n The green \u201crun\u201d gutter icon is the most straightforward way to start debugging any unit test you want. Set a breakpoint in the unit test\u2019s code, click on the icon, select If you run or debug unit tests, a new Run Configuration will be created and launched with a live presentation of the test execution reflecting the structure of the launched tests. There are three node statuses in the tree when the execution is complete: You can click the icons on the toolbar to quickly filter tests with a specific status. <\/p>\n\n\n\n When a test has failed, the Log pane shows the exact message from the assert method and a link to quickly navigate to the failed unit test. Also, for the ignored unit tests this pane shows a description of why the test was marked as You can also rerun the Run Configuration with the test by clicking the Rerun<\/em> icon on the toolbar once you\u2019ve fixed the failed test (or the code tested by the test). Even if you\u2019ve closed the Run<\/em> tool window, you can still rerun the Run Configuration for the unit test via the Run<\/em> applet on the main Fleet toolbar or the Executing In the bottom right corner of the text editor, there is a new selector which allows you to select the target framework for an open file, which adds more context for the code analysis engine. <\/p>\n\n\n\n A similar selector exists for files belonging to a shared project, helping you select the proper context for this file. <\/p>\n\n\n\n Now you can set up project properties for a whole solution via the UI to configure MSBuild to compile and build your projects properly:<\/p>\n\n\n\n You can find them in the We have added two additional keymap schemes. Now, you can choose either the From time to time, everyone needs to demolish something that was implemented incorrectly and start rebuilding it from scratch. That\u2019s what happened here \u2013 we’ve reworked the format for .NET Run Configuration to make it more convenient and unified, minimized duplicated properties (like properties that are already specified inside the If you have already installed the Fleet 1.18 update, all of your old custom .NET Run Configurations have stopped working and you will have to update them manually to support the new format depending on their types.<\/p>\n\n\n\n If your custom Run Configuration has the If your custom Run Configuration has the dotnet<\/em> type, you should do the following:<\/p>\n\n\n\n <\/p>\n\n\n\n We look forward to hearing your thoughts about Fleet in general and its C# support in particular. This will help us shape the product. Here are several feedback channels for you to use:<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2022\/11\/DSGN-14962_CSharp_support_in_Fleet_Blog_Featured_image_1280x600_02.png\")
<\/figure>\n\n\n\nSolution View<\/h2>\n\n\n\n
Solution view tool window<\/h3>\n\n\n\n
.sln <\/code>file) or a .cs<\/code> file from the Files view when Smart Mode is enabled, Solution View will be automatically focused. <\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/solution-view-main.png\")
<\/figure>\n\n\n\nBuild \/ Rebuild \/ Clean actions<\/h3>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/solution-view-build-actions.png\")
<\/figure>\n\n\n\nCreating a new project<\/h3>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/solution-view-new-project.png\")
<\/figure>\n\n\n\nOpen Solution<\/h3>\n\n\n\n
.sln<\/code> files in the open folder or several .sln<\/code> files available in the subfolders. In this case, you can use the Open Solution<\/em> action to specify which solution to work with. At any point, you can use this action to select another solution and add it to Solution View.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/solution-view-select-solution-file.png\")
<\/figure>\n\n\n\nUnit Testing<\/h2>\n\n\n\n
Run unit tests for different scopes<\/h3>\n\n\n\n
![\"Enable](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/unit-testing.png\")
\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/unit-testing-run-test.png\")
<\/figure>\n\n\n\nDebug unit tests<\/h3>\n\n\n\n
Debug<\/code> in the menu, and Fleet will attach the debugger to your test. <\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/unit-testing-debug.png\")
<\/figure>\n\n\n\nRun configurations for unit tests<\/h3>\n\n\n\n
Passed<\/code>, Failed<\/code>, and Ignored<\/code>. <\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/unit-testing-filter-1.png\")
<\/figure>\n\n\n\nIgnored<\/code><\/p>\n\n\n\nRun | Run & Debug<\/code> action from the main menu. <\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/unit-testing-run-configs.png\")
<\/figure>\n\n\n\nNavigate to test source<\/h3>\n\n\n\n
Navigate to test source<\/code> from the context menu on a node in the unit test tree navigates you to the source code so that you can quickly get an idea of the test\u2019s purpose. Double left-clicking also allows you to navigate to a unit test source.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/image-7.png\")
<\/figure>\n\n\n\nBetter support for projects with multiple target frameworks <\/h2>\n\n\n\n
![\"Enable](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/select-target-framework-1.png\")
\n\n\n\nSetting up Solution Properties<\/h2>\n\n\n\n
\n
Debug<\/code> or Release<\/code>.<\/li>\n\n\n\nAnyCPU<\/code>, x64<\/code>, x86<\/code>, or ARM64<\/code>.<\/li>\n<\/ul>\n\n\n\nSolution Properties<\/code> section on the Configure Workspace<\/code> page.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/solution-properties.png\")
<\/figure>\n\n\n\nNew shortcut keymaps<\/h2>\n\n\n\n
Visual Studio<\/code> scheme on Windows or the Visual Studio Code<\/code> scheme on Windows, macOS, and Linux.<\/p>\n\n\n\nBroken Run Configurations<\/h2>\n\n\n\n
launchSettings.json<\/code>), and added useful ones like targetFramework<\/code> and solutionPath<\/code>. <\/p>\n\n\n\n“dotnet-launch-settings” type<\/h3>\n\n\n\n
dotnet_launch_settings<\/code> type, you should do the following:<\/p>\n\n\n\n\n
dotnet-launch-settings<\/code>.<\/li>\n\n\n\nexePath<\/code>, commandName<\/code>, and commandLineArg<\/code> properties, which will be highlighted as errors on the run.json<\/em> file.<\/li>\n\n\n\nsolutionPath<\/code> property.<\/li>\n\n\n\ntargetFramework<\/code> property.<\/li>\n<\/ul>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/05\/broken-run-configs.png\")
<\/figure>\n\n\n\n\u201cdotnet\u201d type <\/h3>\n\n\n\n
\n
solutionPath<\/code> property.<\/li>\n\n\n\nexePath<\/code> property, which will be highlighted as an error on the run.json<\/code> file.<\/li>\n\n\n\ntargetFramework<\/code> property.<\/li>\n<\/ul>\n\n\n\nWe\u2019d love to hear your feedback<\/h2>\n\n\n\n
\n