tinaschrepfer on tinali
Remove use of "any" content typ… (compare)
tinaschrepfer on tinali
Merge pull request #169 from Mi… Add sample support for "any" co… (compare)
tinaschrepfer on master
Update VSSDK package and remove… Merge pull request #169 from Mi… (compare)
Here is a version displaying the latency of the stopwatch surrounding the task running the search:
Normal (task takes ~110ms to search, note how sometimes the treeview won't update until a mouse event on the tool window): https://drive.google.com/file/d/1QxL4J-IzmvnFq7nvZimGORKLx1_eLzqb/view?usp=sharing
UIThreadBackgroundPriority (task takes ~340ms to search): https://drive.google.com/file/d/1vuadQH0wT77dCzR99ho_r860Z-ixfKH3/view?usp=sharing
So, using normal I can run the actual search 3x as fast (as shown in the timer, and visually seeing the progressbar update much quicker), but the TreeView can arbitrarily just not update until a mouse event comes in. Unfortunately this means I have to pick the slower UIThreadBackgroundPriority, in order to avoid the random failures
Ag.RunAgAsynccall (seen inside the gist), however this made things much slower, only in the UIThreadBackgroundPriority case (800ms - 1500ms), presumably because it needs to schedule it on a different thread?
NoSolutioncontext and then registers for the events of interested. The second approach we use is to leverage the Solution Explorer extensibility, which is completely independent of
VSPackageloading. Export an
IAttachedCollectionSourceProviderand Solution Explorer will call your component quite early. In our case, we actually do want to show a custom virtual node in Solution Explorer, so we're going to implement that interface in such a way that it selectively emits new nodes. In your case, you'd just be using it as a hook to do other work.
Hi, I'm trying to update one of my extensions to VS 2022, but it's crashing at the end when trying to open a help page:
The error message is: Method not found: 'EnvDTE.ItemOperations EnvDTE._DTE.get_ItemOperations()'.
Can I replace this with something else?
I am currently working on a custom multi-project template for VS that I want to use a Wizard Extension with in order to prompt the user to selectively generate the projects. To do so, I've implemented a Root Wizard (
RootWizard class) and Child Wizard (
ChildWizard class). The
ChildWizard class is configured in the
.vstemplate file of each project to be generated, and the
RootWizard is provided in a
WizardExtension template in the top-level
.vstemplate file. Both
ChildWizard have some stuff in common...such as Configuration, logging etc. I wanted to derive an ABSTRACT class,
WizardImplBase that implements
IWizard abstractly, and then derive
ChildWizard off of it. When I do so, however, and then run the Create New Project process in VS, then I bump into the error that VS says "There is no RootWizard class in assembly MyProjectWizard.dll".
Do the Create New Project flow and
.vstemplatenot play nice with an abstract base class implementing