The Utilities.cs class is no longer required, you can use the provided HierarchyUtilities class.There is now a MSDN feature suggestion to fix the code sample.
I reported it to Microsoft Connect (the report seems to have been deleted now) and actually what was wrong was the MSDN sample, which should use the SVsServiceProvider parameter type (instead of IServiceProvider type) in this constructor: public FileNameFilterProvider(SVsServiceProvider serviceProvider. I reproduced the issue and after some investigation I concluded that it was a bug in VS 2013, because the version of the Walkthrough for VS 2012 actually worked. The question was that following the MSDN Walkthrough: Extending the Solution Explorer Filter the sample didn’t work for VS 2013 Update 4.
The other day I picked this one about extending the Solution Explorer filter with a custom filter, something that I didn’t know. One of the things that I do from time to time is to take a question in the MSDN Visual Studio Integrate or StackOverflow forums about a subject of VSX that I am not very familiar with, and try to investigate and provide an answer. UPDATE (Jun 16): Thanks to Mister Magoo for pointing in the comments that the problem is that I renamed the setup file from vssdk_full.exe to vssdk2013_full.exe. I don’t have a solution or workaround, though. If this problem happens to you, now you know you are not alone. I don’t know if I am the only VSX developer in the world with this problem (I haven’t seen it reported) but anyway today I have opened a bug report on Microsoft Connect, which includes the screenshot and the log file. When I activate it, running the vssdk2013_full.exe setup with the “Troubleshoot compatibility” context menu, the setup is run with Windows 8 compatibility but still I get the same error. “Windows Program Compatibility mode is on. When I try to install the VS 2013 SDK on Windows 10, I get the following error:
I think I never reported this problem, neither on Microsoft Connect nor on this blog (it seems that I have been very busy last months…), but I have reproduced it on my two Windows 10 machines.
0 kommentar(er)
