Reply to thread

Message

what is the right way to set up plug-in development and deployment

Hi ,

I have a question about the proper way of deploying external plug-ins.
(The system has been installed with all the needed tools and sdk’s and can compile the latest svn fine)

In the last couple of days I’ve tried to start a new plug-in development (just something simple to find out how it all works)
Now I’ve come to completion of phase 1, I would like to deploy it on my entertainment machine and test in real life.

How it started: (wrong I guess)

I added a new plug-in folder in the SVN-updated folder. And went from there. But it seems that compiling like this is embedding the code in the main application rather than creating an external plug-in that can be used on other machines as an add-on or plug-in.
So I isolated the code into a separate project and added all the references to the SVN directory. Compilation went ok.
However the version on my entertainment machine is the so-called Stable 0.2.2.0 version, and copying the plug-in dll in the plug-in/windows folder returns at setup/configuration with the message that the plug-in can’t be loaded because it was made for a different version.

What is the proper way to go from here?

Thanks in advance.

<blockquote data-quote="MSMP" data-source="post: 124791" data-attributes="member: 27012">what is the right way to set up plug-in development and deploymentHi ,I have a question about the proper way of deploying external plug-ins. (The system has been installed with all the needed tools and sdk’s and can compile the latest svn fine) In the last couple of days I’ve tried to start a new plug-in development (just something simple to find out how it all works) Now I’ve come to completion of phase 1, I would like to deploy it on my entertainment machine and test in real life.How it started: (wrong I guess)I added a new plug-in folder in the SVN-updated folder. And went from there. But it seems that compiling like this is embedding the code in the main application rather than creating an external plug-in that can be used on other machines as an add-on or plug-in.So I isolated the code into a separate project and added all the references to the SVN directory. Compilation went ok. However the version on my entertainment machine is the so-called Stable 0.2.2.0 version, and copying the plug-in dll in the plug-in/windows folder returns at setup/configuration with the message that the plug-in can’t be loaded because it was made for a different version. What is the proper way to go from here?&nbsp; Thanks in advance.</blockquote>

[QUOTE="MSMP, post: 124791, member: 27012"] [b]what is the right way to set up plug-in development and deployment[/b] Hi , I have a question about the proper way of deploying external plug-ins. (The system has been installed with all the needed tools and sdk’s and can compile the latest svn fine) In the last couple of days I’ve tried to start a new plug-in development (just something simple to find out how it all works) Now I’ve come to completion of phase 1, I would like to deploy it on my entertainment machine and test in real life. How it started: (wrong I guess) I added a new plug-in folder in the SVN-updated folder. And went from there. But it seems that compiling like this is embedding the code in the main application rather than creating an external plug-in that can be used on other machines as an add-on or plug-in. So I isolated the code into a separate project and added all the references to the SVN directory. Compilation went ok. However the version on my entertainment machine is the so-called Stable 0.2.2.0 version, and copying the plug-in dll in the plug-in/windows folder returns at setup/configuration with the message that the plug-in can’t be loaded because it was made for a different version. What is the proper way to go from here? Thanks in advance. [/QUOTE]