-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C++ projects are not identified as such when running in VS 2017 RC #156
Comments
What interfaces are there when you invoke |
I'll tell you tomorrow (unless I forget) - don't have 2017 on the home PC yet. Bottom line: don't do that. Don't ever give up strong typing unless absolutely necessary. |
Most likely that someone was me. Yes, I agree that having strong typing is good but it all started because different versions of Visual Studio use identical yet formally different sets of interfaces and so having a plugin which supports all of them requires either duck typing or a lot of thunk assemblies and a whole set of Visual Studio SDKs (and Visual Studios too) to build the project. |
Hmm. Sorry, I wasn't aware of that problem. |
Here it is #12 |
Right... So I can't just use the |
If it's part of version-specific assembly - no, you cannot make use of it for strong typing. That's why there's |
If the fast project loading experimental feature is disabled, it works. https://stackoverflow.com/questions/43321647/iterating-vcfilter-tree-in-visual-studio-2017 |
Interesting, thanks. Still, I believe that the proposed changes to the code should allow the add-in to circumvent this issue. |
The plugin fails in VS 2017 RC because the following line in
isVisualCppProject()
always returnsnull
:projectObjectType.GetInterface("Microsoft.VisualStudio.VCProjectEngine.VCProject");
The text was updated successfully, but these errors were encountered: