PlugIns? (#2) - Instructions for deploying/installing a plug-in. (#211) - Message List

I'm not a .Net expert but You need to run Regasm on your component to make it visible to COM. You also neet to be sure that the "set com visible" flag is set in your project.

I suspect your debug version is working because it gets registered automatically as one of the Post Build steps in your project.

You did not mention it but I assume you put an entry in the registry "Client Editors" key under HKLM/SW/PFPS/Falconview.

One tip on debugging is to check the error log: %appdata%\missionPlanning\errorlog.txt

If it fails to instantiate your com object it will report the error code.

Chris

I have learned that the Interop’s do not need to be regasm’d. They should be local in your install directory and but do not overwrite anything installed in the fvw.exe directory.

The real solution for installing and deploying a plug-in is to add a Setup Project to my Solution and add an Installer Class to my plug-in Project. And then code up my Installer Class to check for the next available Client Editor Registry key.

This site gives a step by step for making a Setup Project:  http://www.simple-talk.com/dotnet/visual-studio/getting-started-with-setup-projects/

For the C# Installer Class you do something similar to:

...
using System.Runtime.InteropServices;
using System.Configuration.Install;
namespace MyPlugin
{
   [ComVisible(false)]
   [System.ComponentModel.RunInstaller(true)]
   public class MyInstallerClass : Installer
   {
   ...
   // Containing some "override" declarations
   protected override void OnBeforeInstall(IDictionary savedState) {...}
   public override void Install(IDictionary savedState) {...}
   public override void Commit(IDictionary savedState) {...}
   public override void Rollback(IDictionary savedState) {...}
   public override void Uninstall(IDictionary savedState) {...}
   ...
   }
}

This may be of some help:

 http://giscoder.blogspot.com/2008/11/installing-falconview-client-editors.html

I ran across an interesting problem while installing new versions a plug-in. I am using a .NET installer class as I referenced above.

I uninstall the plug-in using the *.msi. When finished I search the registry for anything referencing the plug-in. Nothing is found ... it looks to be completely removed. Then I install the newer version of that plug-in. It installs correctly.

When I run the plug-in it is the old version running ... not the newly installed one!

I do these same steps on a different PC and it responds as expected. Any ideas?