Mar 30, 2011 at 8:01 AM
Edited Mar 30, 2011 at 8:01 AM
I have had similar issue with Mello.ImageGallery modules. The source of that problem was that the module name (Mello.ImageGallery) differs from assembly name (ImageGallery) and ASP.NET compiled module views to temporary assembly with duplicate classes from
ImageGallery and the exception looked like
The type 'Mello.ImageGallery.Models.ImageGalleryPart' exists in both '
When I renamed module assembly to match module name, that extra assembly was gone along with that exception. Try that. Also, looking inside dll that causes the exception with Reflector may give some clues. Maybe messing with this will also help:
<Target Name="AfterBuildCompiler" Condition="'$(MvcBuildViews)'=='true'">
<AspNetCompiler VirtualPath="temp" PhysicalPath="$(ProjectDir)\..\$(ProjectName)" />
I hope Orchard gurus will give us some insight on what's exactly breaking when the assembly name is different from module name.