12 Replies Latest reply on Jan 20, 2012 12:49 PM by Asle Frantzen

    Releasing Add Ins for other Users

    T13856

      I have created a simple add in using the simple add in template and am having issues releasing the project for use on a different PC. The add in works perfectly fine on my PC however i don't know how someone else can run the add in without opening the project in visual studio and building it themselves (if they dont have visual studio installed for example)

       

      Is there an installer that can be built from the project? I am using visual studio 2010.

       

      Thanks

       

       

        • Re: Releasing Add Ins for other Users
          MvanderVeeken

          I'm assuming you are talking about ProcesBook add-ins.

          • Did you run the AddinReg.reg (the one that is included with the template) file with regedit on the client pc? This makes sure the plugin is registered with ProcessBook in the registry
          • Did you register the plugin assembly (take a look at regasm)
          • Maybe you have an issue with x86 and x64 systems? Is the system you are developing on the same architecture as the other clients? It is possible that the you have registered it in the wrong node in the registry. For x86 systems this is HKEY_LOCAL_MACHINE\Software\PISystem\PI - ProcessBook\Addins\<assembly.name.Connect> , for x64 systems this is  HKEY_LOCAL_MACHINE\SoftwareWow6432Node\PISystem\PI - ProcessBook\Addins\<assembly.name.Connect>

          Having an AddinReg.reg file like this should do the job on both 32 bit and 64 bit systems. Please replace the 'AssemblyName' by the name of your plugin assembly (without the extension).

           

           

           
          REGEDIT4
          
          
          
          [HKEY_LOCAL_MACHINE\Software\PISystem\PI - ProcessBook\Addins\AssemblyName.Connect]
          
          "FriendlyName"="AssemblyName, A new procesbook plugin"
          
          "Description"="Assemblyname let's you extend ProcessBook with this awesome plugin"
          
          "LoadBehavior"=dword:00000003
          
          
          
          [HKEY_LOCAL_MACHINE\Software\SoftwareWow6432Node\PISystem\PI - ProcessBook\Addins\AssemblyName.Connect]
          
          "FriendlyName"="AssemblyName, A new procesbook plugin"
          
          "Description"="Assemblyname let's you extend ProcessBook with this awesome plugin"
          
          "LoadBehavior"=dword:00000003
          

           

           

           

           

           

            • Re: Releasing Add Ins for other Users

              Typically people would build a simple installer to deploy those add-ins. You can add a "Setup Project" to your add-in Visual Studio solution and build an .msi. Then you can distribute this .msi or even include it in your PI ProcessBook deployments, if you are using standard Microsoft deployment tools (e.g. SMS, group policies).

                • Re: Releasing Add Ins for other Users
                  T13856

                  So i think the issue is with registering the assembly. If i run the vs command prompt and run regasm.exe to create a .reg file to register the assembly do i need to then edit that to point to the Local Machine like the Addinreg.reg does?

                   

                  I've tried various iterations of this process and my addin has unsuccessful loaded.

                   

                  Furthermore do i need to copy any other files to the directory C:\Program Files\PIPC\Procbook? On my PC that directory doesnt contain any dlls. Simply building the project once makes it work (and only registering using the Addinreg.reg file)