-
My integration journey has come to an end. For my last post, I am going to write about a new way of loading VSTA AddIns: MEF. I have talked about MEF some in my previous posts , and have successfully used both VSTA and MEF together before. This time, I have successfully used MEF to load VSTA AddIns. To do this, I had to edit part of the MEF library
-
This is one of my last posts in this series. If you have not yet read my previous posts, here are the links to them: Chapter One , Chapter Two , Chapter Three , Chapter Four . (I would especially read Chapter Three, as that is where I introduce MEF, and I would also read the MEF Overview and the Programming Guide, which are linked to in Chapter Three
-
Q : The VSTA IDE keeps hanging up while debugging when I try to step into code. Why is it doing this? A : The IDE may be hanging because you have left PDB files in your application directory. Even if you are running the Release version, make sure that you have no PDB files in the same directory as your application.
-
My integration journey is taking some exciting turns. As always, I would encourage you to read the first three posts in this series ( Chapter One , Chapter Two , and Chapter Three ) before reading this one. I have finally integrated the VSTA IDE into my Contact Manager program. I am going to go through how I did this, show some code, and talk about
-
Q : I have a problem with loading VB add-ins. The method call: ObjectModel::Collection<AddInToken^>^ addInToken = AddInStore::FindAddIn(IEntryPoint::typeid, AddInStoreExtensions::DefaultPipelinePath, FilePath, TypeName); returns an empty collection when called on a dll created using VB. The FilePath parameter points to a dll, the TypeName is an
-
In this sample, Melody modified the proxy to include an entry point for the CDocDrawing class (the CDocDrawing class was also modified to include events which become disassociated with ProxyGen- see this blog for related info on this bug ) and the HostItemProvider to expose the CDocDrawing type. Melody also created a template for document level add
-
In this sample, Melody modified the proxy to include an entry point for the CDocDrawing class (the CDocDrawing class was also modified to include events which become disassociated with ProxyGen- see this blog for related info on this bug ) and the HostItemProvider to expose the CDocDrawing type. Melody also created a template for document level add
-
For chapter three, I will be introducing a framework from Microsoft called the Managed Extensibility Framework, or MEF ( MEF on CodePlex , MEF on MSDN ). If you are not familiar with MEF, you will certainly get more out of this post if you read the MEF overview and programming guide ( MEF Overview , MEF Guide ). Now I will give a synopsis of what has
-
Here is the second chapter in my integration journey. If you have not looked at the first blog post , it would be a good idea to look there first, because that post will explain the application I am working with and my idea behind it. First, let’s look at a few things that have changed since my first app. If you open the attached .zip file , you
-
Here is Microsoft’s workaround for the problem hang-ups during in-process debugging: “The idea is that we want to wait for the type –registering threads to finish before we call addin.FinishInitialization. What I did is to record the number of threads in the process before we activate add-in. After addin.Initialize (when the type-registering