Hi Folks,

 

I have a problem with a module that I created and installed using In-Place deployment or what Michael Washington calls WSP. This type of deployment includes the source code for the module and not the dll. JIT compilation takes care of the rest. Why? – Because I was getting a BC30456 error. This thread explains it if you are interested - http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/137621/scope/posts/threadpage/1/Default.aspx.

 

The In-Place or WSP compile was working just fine. However, I added a text box to two of my pages for an additional filter on a GridView. The module project compiled OK so I packaged it up in a zip file and uploaded it to the test DNN site on my local machine where I check things out before uploading to the host. That worked but when I tried to add the module to a page I got a “Could not load the assembly” error. Strangely if I use the dll and web page deployment without the source files method (sometimes called WDP) the module can be added to a page and it works! Unfortunately due to the BC30456 error I can't use that method on my host site! I have tried clearing everything including the temporary internet files built by ASP.NET 2.0. I think this might be a JIT compile problem but I can’t determine why. Has anyone had a problem like this with a custom module? Do you think this is a DNN or an ASP.NET 2.0 issue?

 

Any advice would be most appreciated.

 

Thanks,

G. M.  

Thanks for the quick reply. I don’t think that is the problem but maybe it could be. I am working with a test installation. Possibly I added something or did an upgrade since I last worked on this module. I’ll check out the namespace conflict angle. If it isn’t that, it could be something similar.

 

Thanks,

G. M.