Asked — Edited

Myfirstplugin Error. Misssing Dll Or Incorrect Filename Specified In Plugin.Xml

So I followed @DJ's excellent tutorial on creating an ARC plugin... (the 2 servo button window).... Everything went great, no compiler errors and everything looks exactly like @DJ's tutorial... GUID is correct, folders and dll are where they are supposed to be and reference name (DLL) in the xml file seems correct... It even shows up in the beta section of ARC.... But when I try to add the plugin to my project I get this error... "misssing DLL or incorrect filename specified in plugin.xml"

User-inserted image


ARC Pro

Upgrade to ARC Pro

Stay at the forefront of robot programming innovation with ARC Pro, ensuring your robot is always equipped with the latest advancements.

PRO
Synthiam
#1  

That's an easy one - the filename of your DLL in the plugin.xml is incorrect:) As the message says

#2  

Ha, ha, "easy one" ... some how I knew you were going to say that... Ok let me rephrase LOL... I know what's wrong, just not why it's wrong... For the life of me I can't see why the file name (MyFirstPlugIn.dll) is incorrect when that is the name that I have in my plug in folder of the DLL file... Here is my plugin.xml file....

<?xml version="1.0" ?> <PluginV1XML xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">; <FRIENDLY_NAME>MyFirstPlugin</FRIENDLY_NAME> <DLL_FILENAME >MyFirstPlugIn.dll</DLL_FILENAME> <AUTHOR_NAME>Richard R</AUTHOR_NAME> <LICENSE_URL>https://synthiam.com/tutorials/plugin-license.aspx</LICENSE_URL>; <PLUGIN_GUID>233f4787-4d44-4ec7-8b4c-00aace3d1f30</PLUGIN_GUID> <CATEGORY_TYPE>Beta</CATEGORY_TYPE> <DESCRIPTION /> </PluginV1XML>

PRO
Synthiam
#3  

Maybe it's case sensitive?

*Edit: i'm just waking up and so is my brain. I should have not suggested that. There is no case sensitive in Windows.

Show me a screenshot of your output folder where the plugin.xml is.

#4  

I copied and pasted the MyFirstPlugIn.dll file name into the xml file and saved it... Compiled my project again. I then went to my Visual Studio project folder and found the plugin.xml file... copied it and pasted it into the ez robot plugin folder of my unique plugin (with MyFirstPlugIn.dll already being there) GUID... I have done something wrong somewhere.... I guess I could delete the plugin and start over...?

PRO
Synthiam
#5  

You should not need to delete the plugin and start over.

The files will copy themselves to the build output folder when you build the project (CTRL SHIFT B). You do not need to copy the files manually.

I suspect the path is incorrect - what is the exact path to your output folder? For example...

[feature] C:\Users\Public\Documents\EZ-Builder\Plugins\60db819e-e6ab-4d18-89eb-b253f1bb4183 [/feature]

#6  

The output path looks weird even though I navigate to the correct ez robot plugin folder it always defaults to what you see below...

User-inserted image

the output folder as I enter it before saving...

User-inserted image

#7  

The exact path is "C:\Users\Public\Documents\EZ-Builder\Plugins\ 233f4787-4d44-4ec7-8b4c-00aace3d1f30"

PRO
Synthiam
#8  

I see a space in your path:) Right before the 233 of the GUID. The directory containing your output path has a space in it.

For example, you specified this... [feature] C:\Users\Public\Documents\EZ-Builder\Plugins\ 233f4787-4d44-4ec7-8b4c-00aace3d1f30 [/feature]

The correct path should be this...

[feature] C:\Users\Public\Documents\EZ-Builder\Plugins\233f4787-4d44-4ec7-8b4c-00aace3d1f30" [/feature]

*Note: I highlighted in BOLD where the error is in your OUTPUT PATH declaration. There is a blank space in the directory name of the GUID.

  1. Load the properties of the visual studio project

  2. Locate OUTPUT PATH

  3. Remove the space at the beginning of the GUID

  4. Close the properties and save your project

Now that you have corrected the path, the old output folder (the one with the space) will still exist in the PUBLIC Documents folder. You will manually need to delete that folder (the one with the space). Otherwise two plugins will show up and one won't work.