2.6 - Custom Plugin not showing up in the list (works fine when debugging)

how are you running the published files?  Uploading to a server?

Have you tried running it/building the published files locally first in VS and IIS7.5 express once you've copied over your plugin folder with just the dll and Description.txt in it?

Time to retrace your steps.

par6 wrote:

I have folders similar to this  C:\SourceFiles and a folder C:\Website on the same server. Thats why I'm so baffled as when i run from the source files it works fine, when I run from the deployable code base deploy.bat produces, it doesn't.

I have also tried removing all files other than the dll and description file, still no luck.

I would suggest you install/deploy a "no source" version of nopCommerce, and then deploy your plugin to it (create plugin sub folder, copy into it your dll)

but first...
re: " massive list of DLLs being deployed with the plugin"
Delete them.
You should be sure that "Copy local" is set to false for all your References.  (highlight all your refs, right click, properties)

I am also facing the same issue with NOP2.65code, third party plugins are not getting copied to plugin folder.
It works when I manually copy the plugin to plugin folder. It was working fine with 2.60 but 2.65 does not work for deploy.bat file.

hiya


I had a plugin not showing up in the list, I tried lots of things to get it to work.

so I copied the whole zip over to the root folder on my server and unpacked it there.
Presto it showed up 1st time.

Locate the source code folder and remove the read only file attribute recursively. This should get things building as expected.

In case anybody is Googling why their custom plugin can't be found here's another thing you can check:

I managed to create a plugin (by copying an old version) in the wrong physical location. I loaded the plugin as a project in Visual Studio with no problems and it compiled, but, because the output directory is specified as a relative path, the compiled code never showed up in the Nop.Web/Plugins directory.

It wasn't until I found a copy of the pdb and dll files in a completely unexpected place that I realized what had happened.