Creating I/O Module From Project Template

[ss52642]

I have found an issue when creating an I/O module using the project template.  In the ProjectTemplate\MetaData\NISE_DataEngine.xml file, the MetaDataClass field for the I/O module is pointing to a file that does not exist.

Original

<MetaDataClass>scripting/DCAFConfigurablePluginDecideFeatures.lvclass</MetaDataClass>

Fixed

<MetaDataClass>scripting/TagBusConfigurablePluginDecideFeatures.lvclass</MetaDataClass>

When I changed mine to call the fixed path I see the correct spec page but it gives me an error saying a file path is too long when creating the project.

[ss52642]

Here is an image of the error.  It doesn't look like it attached to my original post.

[MattP]

Indeed, this does affect the version out on tools network.  I've added an issue on the Github repo to track this.https://github.com/LabVIEW-DCAF/DCAFSampleProjects/issues/36

Can you help me quantify the severity of this for you?  (i.e., is this holding up production or project deadlines, or just an annoyance keeping you from experimenting with the templates)

[ss52642]

Right now this is just an annoyance

[MattP]

Thanks for reporting the issue.  We have some other pending changes to the templates that are in work, so it will take a little while before we can roll out a fix to this.  Broken templates are obviously a problem, and we will address it as soon as possible.

[MattP]

FYI, to repair the issue on your system, you can follow these steps:

Leave the XML file as is (referring to DCAFConfigurablePluginDecideFeatures.lvclass).

Create a new project in LabVIEW.

Add the TagBusConfigurablePluginDecideFeatures.lvclass

Right click on the class, Save As.  Rename the class file to DCAFConfigurablePluginDecideFeatures.lvclass in the same folder.

Right click on the class, choose Save All (this class).

Close the project (no need to save the project).

This will permit creation of the sample project.

Once the in-flight code edits to the template are complete in our development branch, we'll merge in these changes for the next release.

[MattP]

Ok, I believe we have a fix in place.

Can you please install this package and verify that it does indeed resolve this issue?

[ss52642]

that works

[MattP]

Thanks.  I'll roll it into the main branch so it will go out on Tools Network with the next batch of updates.  If you see any other annoyances, please let us know so we can fix them.