Hi all,

First of all, this is the first ever DNN module I've developed so, if you find something that makes you say "dude, what?" is because of that fact. I have a main database from which we all get our data off and set data. There is an API that was developed so that we could interact with the database and this API uses Microsoft.ApplicationBlocks.Data v.2.0.0. I wasn't even able to finish my module (following the steps outlined here) when I noticed that my development server went for a stroll saying "System.IO.FileLoadException: Could not load file or assembly Microsoft.ApplicationBlocks.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)". All references to the API have been removed but it doesn't get over it, it still complains about the same thing. It is mandatory to use that API, so, what can be done for DotNetNuke and the API to work?

Thanks in advance,

Garbimba

Hi Michael,

This is when the whole thing started. I tried to create my first dynamic module, the folders where created, life was good. Then I went on to reference my APIs so they will be added to the "Bin" folder of the portal. After that I changed the namespaces names on the created classes to my own names. Right after that I got lost among the different files created by the starter kit so I stepped back trying to figure out how it all worked. Then some changes on the page's text had to be made and then is when it all failed. To get back running, first I tried to delete the references to my API; didn't do it. Then I made a copy from the production machine and life was good again. Now I don't know where the extra reference was made and I'm hesitant of making another module. Where was my mistake and if so, how can I do ti better now?

Thanks,

Michael,

Inserting your business logic into your presentation layer isn't something that should be encouraged. Though your suggestion solves, in a way, the problem, it just avoids the problem. Using the steps outlined in your guide I was able to easily create a module but when I went to reference the library at the project level it just broke again. Do you, or anybody, have another idea?

Thanks,