Adding reference to plugin causing system name is already defined

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
5 years ago
I am building a plugin that depends on the functionality of another plugin in my project. When I import the plugin as a dependency into my references of my plugin, I receive the following error message:

A plugin with 'Payments.CreditCardPayment' system name is already defined


I have turned off building in my solution for that project, however, the views no longer work as they're dependent on the view files being copied over.
5 years ago
I worked it out instantly after posting this.

In your plugin > dependencies > projects > right click on plugin project > set property 'copy local' to 'no'

Hope this helps someone.
2 years ago
Eyre wrote:
I worked it out instantly after posting this.

In your plugin > dependencies > projects > right click on plugin project > set property 'copy local' to 'no'

Hope this helps someone.
thanks . it worked.
2 years ago
I added this extra to Nop.We.csproj file

  <ItemGroup>
    <!-- This setting fixes the problem caused by this update in the websdk in vs2019
    https://github.com/aspnet/websdk/commit/7e6b193ddcf1eec5c0a88a9748c626775555273e#diff-edf5a48ed0d4aa5a4289cb857bf46a04
    Therefore, we restore the standard configuration behavior (there was no copy to the output directory)
    in order to avoid the "Duplicate dll" error during publication.
    We can also use “ExcludeConfigFilesFromBuildOutput” according to https://github.com/aspnet/AspNetCore/issues/14017 -->
    <Content Update="**\*.config;**\*.json" CopyToOutputDirectory="Never" CopyToPublishDirectory="PreserveNewest" />
  </ItemGroup>
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.