I am getting this error when I run an extension against EVS. I have set the basePath to the bin in the manifest file, and the package installs correctly. Here is a link to the errors being generated by EVS, http://evs.dotnetnuke.com/results.htm?fileId=c3a2978d-8fe8-4058-8cc8-d17c457da4b4. The .dll files are all correctly placed in the bin folder, but EVS cannot find the files.

Thanks,

Joshua

Thanks for your help, instead of using BasePath for the assemblies, I added a path pointing to the bin for each individual assembly, and the errors went away.

Thanks,

Joshua

Hello,

Perhaps I didn't explain this well enough. The problem is that if you look at some of the other component nodes for example the File Component which is documented here: http://www.dotnetnuke.com/Resources/W...

You'll see that inside the "files" node pair and before the "file" node pair there is a "basePath" node pair. this node is used to tell DNN where to place each file following relative to the base path of the installation.

The problem that occurs often regarding the Assembly type component is that people often include a "basePath" node, when in fact that node is not applicable in an Assembly component as every assembly is automatically placed with in the bin folder.

This leaves two options for an Assembly node, you can first specify just the name and place the assemblies in the root of the install package, or you can place the assemblies in a sub directory then specify that sub directory using the "path" node.

EVS Already processes this correctly and there is no need to make any updates to it regarding this.

Cheers,

Nathan Rover