• State Not Answered
  • Replies 4 replies
  • Subscribers 389 subscribers
  • Views 2569 views
  • Users 0 members are here
Options
Related

Error when building a Studio 2015 plugin project

Rihards K

Hello,

After creating a separate version of my SDL translation provider plugin project for Studio 2015 as described here i get errors when building the project:

Error 13 The "DeployPluginPackage" parameter is not supported by the "CreatePluginManifestTask" task. Verify the parameter exists on the task, and it is a settable public instance property.

and

Error 14 The "CreatePluginManifestTask" task could not be initialized with its input parameters.

Fiddling with the minversion value in the pluginpackage.manifest.xml file, cleaning/rebuilding the project and restarting Visual Studio (not necessarily in this order) sometimes helps to succeed in building the project, so I can get a working Studio 2015 version of my plugin, but this is far from being a reliable solution as this often works only after many retries if it works at all.

The original project builds just fine.

I have witnessed the same error messages in the Studio 2014 version of my plugin project. But in that case restarting Visual Studio and rebuilding the project always helped.
Rate translation
×
Suggest better translation
×
Parents Reply Children
  • 0 in reply to Romulus Crisan (former member)

    Tried it. As far as I can tell changing the line as you suggested makes no difference.

    Maybe some extra information about my project setup might be relevant. I have a solution with a project for Studio 2009/2011 which contains the plugin code-base and with two separate projects for Studio 2014 and Studio 2015 with (as you might have noticed from the posted .csproj file) .cs files that are linked to the Studio 2009/2011 project. Only the .cs files are shared. All projects have separate resources, resources files and the pluginpackage.manifest.xml file.

    Now it seems that the only sure way to build the project when the errors occur is to clean the Studio 2015 project, restart Visual Studio and to rebuild the Studio 2015 project separately. It seems that this works every time. Building the whole project together by hitting F6 more often than not leads to errors.