Major Host/Test environment Compile problems (Error BC30456) - Extend It! ( Programming in VS2005 & 2008, ASP.Net 2.0 )

Forum General DotNetN... Extend It! ( Pr... Major Host/Test environment Compile problems (Error BC30456)

5/25/2007 10:03 AM

	Michael Washington
2842 posts
ADefWebserver.com

Re: Major Host/Test environment Compile problems (Error BC30456)

WSP is the method used here: Super-Simple Module (DAL+) You simply depoy the .vb (or .cs) files to the production server. Works great. Obviously no one can get to the code from the outside. If you need to update a page you just ftp the change for the one file.

I have not had any errors with the Dynamic Placeholder control. Also, I have only had the error on a windows 2003 server.

Michael Washington
* ADefWebserver.com
* DNN Module Developer's Guide
* IWEB - DNN Web Services
* Silverlight and DotNetNuke

5/25/2007 2:14 PM

	George Mitchell
99 posts

Re: Major Host/Test environment Compile problems (Error BC30456)

Thanks, Michael

So, WSP is a full source deployment. I have also seen it referred to as in-place deployment. I guess it is another option but at this point it seems compilation is my problem so I am not sure adding the VB files would help. At any rate I am making incremental progress. I am in the middle of one of my brute force debug options. I copied the entire web site from my hosting company server, set up the database, set up IIS 5.1, changed the alias in the PortalAlias table, the web.config, etc. I typed in the local url and everything works fine except my module. I get the exact same BC30456 error. That means the mix of DLLs or whatever is most likely the problem. Now I’ll have to go through methodically and compare the site that works with this copied one. I can try various options including the full source on this copy to see what works.

5/25/2007 2:27 PM

	Michael Washington
2842 posts
ADefWebserver.com

Re: Major Host/Test environment Compile problems (Error BC30456)

Modified By Michael Washington on 5/26/2007 8:40:42 AM)

This sounds like the problem I had (it was a non DNN site). The .dll that the pages inhereited from had to be placed in the /bin when the new code that inherited from it was placed in the /bin even if the .dll had not changed! This made no sense until you consider that with ASP.NET 2.0 the assemblies are not executed in the /bin. They are "shadow copied" to another directory. It appears that the base class was not "shadow copied" when the new assembly that inherited from it was placed in the bin.

Michael Washington
* ADefWebserver.com
* DNN Module Developer's Guide
* IWEB - DNN Web Services
* Silverlight and DotNetNuke

5/25/2007 10:31 PM

	George Mitchell
99 posts

Re: Major Host/Test environment Compile problems (Error BC30456)

Michael,

Thanks very much for your help on this. Your analysis is very close to the mark. I have read that the BC30456 error can also occur if you have a mix of modules that have been compiled under VS2003 and VS2005. I think something like that may be the problem in my situation. Here is what I have determined so far by my testing.

I have finally gotten my module to work under two specific circumstances. It definitely indicates why it worked for me all along but not on the hosting server. I have several test DNN installations on my machine. I noticed that every single installation that did not work on my machine and on the host server was an installation from the DotNetNuke_04.05.01_Install.zip file. In the case of the host server I am pretty sure they used DotNetNuke_04.05.01_Upgrade.zip but I am not positive. I tested on two installations that were created using DotNetNuke_04.05.01_Source.zip. Both of those work flawlessly. There was one stipulation, however. I had to compile the code with VS2005. I tested on a second one because I noticed that I had compiled the one I use all the time under debug so I installed another site with the DotNetNuke_04.05.01_Source.zip file. Initially I just ran the site, installed my module and tried to add it to a page. It failed with a BC30456. I then compiled it as production so debug would be out of the mix. When I add my module to a page it worked so compiling everything under VS2005 works.

I suppose I could create my own DotNetNuke_04.05.01_Install.zip and give it to the hosting company but I would guess they would want to get any new version from the DNN team. Besides there may be other considerations I am not aware of. I guess it only happens in rare circumstances. Maybe it occurred for me because I am using the new ASP.NET 2.0 GridView component. BTW the hosting company is PowerDNN so I’ll put in a ticket and point Tony Valenti to this thread. If you have any other thoughts on this let me know.

5/26/2007 6:45 AM

	Michael Washington
2842 posts
ADefWebserver.com

Re: Major Host/Test environment Compile problems (Error BC30456)

Yeah in my situation the base clss was VS2003 and the problem didn't start happening until we upgraded to VS 2005.

I'm pretty sure all this is eliminated if you use the WSP model (deploy the module using the .vb or .cs source code). If that is an option you can avoid this headache.

Michael Washington
* ADefWebserver.com
* DNN Module Developer's Guide
* IWEB - DNN Web Services
* Silverlight and DotNetNuke

Page 2 of 3

Forum

General DotNetN...

Extend It! ( Pr...

Major Host/Test environment Compile problems (Error BC30456)