Hi everyone,
I am looking for some direction or information regarding Single-File Intellisense within VS 2015 when mixed with a VsPackage monitoring an already open solution/project.
I happened across a blog post - https://blogs.msdn.microsoft.com/vcblog/2015/04/29/single-file-intellisense-and-other-ide-improvements-in-vs2015/ from a while back while researching an issue. There were some side-effects that I was hoping to get some help.
When a single-file is opened in an existing Solution/Project, it will trigger IVsSolutionEvents.OnAfterLoadProject() within a registered VsPackage. There is some existing code I inherited which checks for and ignores projects named "Miscellaneous Files" with an empty GUID for project type. That has worked in previous versions of VS.
However, this no longer appears to be the case within VS 2015. On files opened from outside a project/solution's path, the project's type is now a valid type (instead of an empty GUID). My guess is the 'dummy' project that is created for Single-File Intellisense requires a project type in order to determine what mark-up to display on the file.
Can anyone comment on the preferred manner in which one can take an IVsHeirarchy and determine if the originating project is a "Miscellaneous Files" project using what is available in the VsPackage interfaces?
Thank you for your help.
I am looking for some direction or information regarding Single-File Intellisense within VS 2015 when mixed with a VsPackage monitoring an already open solution/project.
I happened across a blog post - https://blogs.msdn.microsoft.com/vcblog/2015/04/29/single-file-intellisense-and-other-ide-improvements-in-vs2015/ from a while back while researching an issue. There were some side-effects that I was hoping to get some help.
When a single-file is opened in an existing Solution/Project, it will trigger IVsSolutionEvents.OnAfterLoadProject() within a registered VsPackage. There is some existing code I inherited which checks for and ignores projects named "Miscellaneous Files" with an empty GUID for project type. That has worked in previous versions of VS.
However, this no longer appears to be the case within VS 2015. On files opened from outside a project/solution's path, the project's type is now a valid type (instead of an empty GUID). My guess is the 'dummy' project that is created for Single-File Intellisense requires a project type in order to determine what mark-up to display on the file.
Can anyone comment on the preferred manner in which one can take an IVsHeirarchy and determine if the originating project is a "Miscellaneous Files" project using what is available in the VsPackage interfaces?
Thank you for your help.
Jeff Clausius - SourceGear