File Explorer in Visual Studio - Potential New Feature
When working with projects in Visual Studio, developers often find themselves needing to access or modify files that aren't directly included in their project or solution. Files like .gitignore, .gitattributes, Dockerfile, or even certain folders like bin or obj might not appear by default in the Solution Explorer. In a recent video titled File Explorer in Visual Studio - Potential New Feature, Tim Corey walks us through a potential solution that Microsoft is testing — a new File Explorer extension for Visual Studio.
This article explores Tim’s detailed walkthrough, insights, and suggestions from the video, providing a practical guide for developers interested in this feature. Let’s dive into Tim’s demonstration to understand the use case, the limitations of current solutions, and how this extension can solve real-world pain points.
The Problem with Accessing Hidden Files in Visual Studio
At the beginning of the video, Tim Corey highlights a common developer frustration — the inability to easily modify files that aren't formally included in the solution. For example, accessing a .gitignore file or editing project-related documentation like README.md becomes unnecessarily complex. Tim explains that one typical workaround is to click the “Show All Files” icon in the Solution Explorer.
However, as Tim demonstrates at 1:21, using this feature creates a cluttered experience. It’s inconsistent, requiring you to activate it for each project individually. You lose cohesion and end up constantly toggling views. Worse, it doesn’t always help at the solution level — for example, you still can’t access files that aren’t part of a specific project but exist in the root solution directory.
Folder View: A Limited Alternative
As a workaround, Tim suggests switching to Folder View (2:00), which does give access to hidden files like .gitignore and .gitattributes. But Tim also makes it clear that this mode has serious limitations. You're no longer in the standard solution view, which means losing access to common tools and functionality developers rely on.
Tim shares his personal opinion here: he doesn’t like switching to Folder View. It feels disconnected and clunky for typical workflows. This leads to his introduction of a much better solution — a new Visual Studio extension currently being tested.
Introducing the File Explorer Extension
To solve these issues, Tim points to a new extension called "File Explorer" by Mads Kristensen, available via Visual Studio’s Extension Manager. As Tim mentions at 2:31, Mads is known for creating experimental features in the form of extensions to gauge interest and collect feedback before Microsoft decides whether to integrate them directly into Visual Studio.
At the time of recording, Tim points out the extension had over 3,000 downloads and a high average rating, suggesting that the developer community finds it genuinely useful.
Installing and Activating the Extension
Tim demonstrates the installation process, mentioning that the extension requires a Visual Studio restart after installation (3:06). After doing that off-camera, he returns (3:16) to show the new File Explorer view now embedded inside the Solution Explorer — a game-changer.
This new section appears as a folder with the solution name and sits at the same level as all your projects. When expanded, it gives direct access to the entire folder structure — even those files and directories that wouldn’t normally appear in the Solution Explorer.
Navigating and Modifying Hidden Files
At 3:29, Tim begins navigating this new File Explorer pane. He demonstrates how it shows everything — .gitignore, .gitattributes, README.md, and more. As he clicks on README.md, Tim edits the file directly inside Visual Studio, praising how convenient and seamless the experience is.
Tim emphasizes this again at 4:01, noting that this new feature blends the best of both modes: the full visibility of Folder View, and the structured, feature-rich Solution View developers prefer.
Additional Features and File Operations
Another practical highlight Tim shows (4:03) is the right-click menu within this File Explorer. Users can:
Open a file in VS Code
Open it in the File Explorer
Open with a default program
Rename the file
- Copy the full path
These features empower developers to manage project-related files directly, without jumping between external editors or file explorers.
Tim particularly notes the time-saving nature of this functionality, especially for files like .gitignore, which often require small but critical changes. As he says at 4:22, you just open the file, make the change, and move on — all without disrupting your usual flow.
Keeping Your Workspace Clean
Tim also shows a neat trick for keeping the interface tidy. You can minimize the File Explorer section, where it then consumes only one line of space at the top of your Solution Explorer. This ensures it’s always available when needed but never in the way when not.
According to Tim (4:36), this makes the tool “quick and easy” to access, while also being non-intrusive — a balance many Visual Studio features struggle to achieve.
Microsoft’s Strategy: Testing Features Through Extensions
At around 6:00, Tim explains why this feature is currently an extension and not a core part of Visual Studio. Microsoft is increasingly experimenting with user-driven development. Instead of guessing what developers want, they release features as extensions to measure real-world usage and feedback.
Tim appreciates this strategy. He points out that sometimes only a vocal minority requests a feature, and integrating it prematurely into the IDE could backfire. By using extensions as prototypes, Microsoft gathers solid evidence before committing to full integration.
How You Can Influence Visual Studio’s Future
Tim encourages viewers to download, test, and provide feedback on the extension. At 6:26, he explains that user engagement — like reporting bugs, suggesting improvements, and rating the extension — helps Microsoft decide:
Whether the feature is worth integrating
- How best to implement it for the broader developer base
Tim also invites suggestions for additional functionality. For example, maybe you’d like drag-and-drop support or a right-click option to “Add to Solution”. These ideas might shape the final implementation, so your input matters.
Final Thoughts and Why It Matters
Toward the end (7:25), Tim sums up his thoughts. He believes this extension solves a real-world developer problem — not one that occurs every day, but one that’s frustrating when it does. For example, modifying the README.md file quickly without jumping to another tool is immensely helpful.
Tim also reflects on how Visual Studio Code sets a strong precedent here. VS Code makes file structure a central part of the interface, and this extension helps bring some of that ease-of-use into Visual Studio — without breaking its core design.
He concludes by emphasizing that although Visual Studio can’t simply become VS Code, it can certainly borrow its strengths. This extension is a step in that direction.
Conclusion
The File Explorer extension for Visual Studio, as presented by Tim Corey in his video, is a smart, efficient solution to a common workflow issue. By allowing developers to access and edit all project-related files — even those outside the scope of the solution — without leaving the IDE or breaking their workflow, this tool bridges an important gap.
Whether you're frequently tweaking .gitignore, editing documentation, or just need visibility into your full folder structure, this extension adds real value. As Tim recommends, try it out, share feedback, and help shape the future of Visual Studio development.
As Tim puts it best, this isn't about solving a daily issue, but solving one that becomes painful when it arises — and doing so in a way that's clean, lightweight, and developer-friendly.
