Your .NET work has outgrown the solution 😱 CI pipelines, GitHub workflows, and a growing number of Markdown files for your agents are all part of your day-to-day workflow, but they usually live outside your solution. Keeping those files within easy reach doesn't mean you should clutter your solution with them. Recently, we asked which view you use, Solution Explorer or File System. Several of you mentioned constantly switching between the two depending on the task. The new Files view in Rider replaces the old File System view. While the previous view was limited to the directory containing your .slnx file, the Files view lets you browse your entire repository, including files and folders outside that directory. Plus, Search Everywhere now indexes files available in the Files view. Even if your solution sits several folders deep, repository-level workflows, agent instructions, and frontend projects remain easily accessible. You can browse and edit them alongside your code without adding solution items or maintaining virtual folder structures. The Solution Explorer view remains the best place to focus on your .NET projects, but when you need to inspect a workflow or check a specification updated by an agent, switch to the Files view and then go back to your project work. Browsing and basic editing are lightweight by default, so Rider won't automatically index your whole repository. For frontend projects that are not part of your solution, such as a React application, you can turn on full IDE support when required. Try the new Files view in the latest Rider 2026.3 EAP build. You'll find it right next to the Solution view. jetbrains.com/rider/nextvers…