![]() Developer Community is the recommended place to vote and create any issues. If you see unexpected behavior, then see the known issues for the release of interest. Open Folder and the .* APIs are under active development. Build - Build support for Open Folder workspaces.įeatures that use the following types will need to adopt new APIs to support Open Folder:.Language services - Integrate language services into Open Folder workspaces.Indexing - Collect and persist data about Open Folder workspaces. ![]() File contexts and actions - File specific code intelligence provided through file contexts.Workspaces - The starting point of Open Folder extensibility is the workspace and its APIs.Extensions can use these APIs to provide functionality for many areas, including: The Open Folder APIs are under the .* namespace and are available for extenders to produce and consume data or actions around files within Open Folder. With Open Folder, Visual Studio gives users a new way of interacting with their source code. Scripting languages and open-source code written in C++ for Linux are good examples. Not all codebases are well represented in a project and solution structure. It's through these hierarchies and capabilities that other components do work on behalf of the user. It understands what files its project contains, the visual representation of the project contents, dependencies on other projects, and modification of the underlying project file. A project system is responsible for the functionality and user interactions of a loaded project. Historically, Visual Studio only understood files in a solution and its projects using project systems. Current extenders can update their existing Visual Studio features to understand code without the backing of projects or a solution. There are APIs to support building, debugging, and symbol search for any file in a user's codebase. ![]() With Open Folder, extension authors can create rich features for any language.
0 Comments
Leave a Reply. |