Hi,

 

I am getting the same compile problem (error BC30456) on my host but not my test system that was plaguing me about a month ago. Here is the thread for that problem:

 

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/121058/scope/posts/Default.aspx

 

At that time I had the hosting guys upgrade me to DNN version 4.5.0. That "solved" it but I never really understood why. Now the problem is back but an upgrade to 4.5.1 has not given me the same result. I wasn’t surprised. The issue revolves around a module that contains an ASP.NET 2.0 GridView. I decided to make some code changes to some event methods in that module just to see what would happen. They did seem to eliminate the problem for specific methods but another one always occurs after the change.

 

Here is an example:

 

 

Here is an example of the type of changes I made. I altered a link button like the following

 

 

to this

 

 

I then added Handles DocuList.Click to the DocuView_Click method in the code beside. It changed where I was getting the error but I don’t think it really fixed anything. Both of these coding approaches should work.

 

The original code as well as every one of my changes compiled, ran flawlessly, and continue to run flawlessly on my test site but not on the host.

 

For deployment I am using partial compilation which compiles the code beside files and leaves the aspx and ascx pages to compile at run time. I create the deployment dll and aspx and ascx pages using the Web Deployment Project (WDP) method. I then package everything up with the .dnn file into a zip file for the DNN installation. This has all worked very well for other modules and a couple of versions of the current problem module until last month. I use the exact same zip file to install on the host and test sites. That seems to work and has worked from the beginning. It is when I actually install a module on a page that I get the problem (BC30456).

 

Now there are obviously differences in the two environments. I do my testing on a desktop machine running Win XP Pro with VS 2005, SQL Server 2005, and IIS 5.1. I know others have had this problem or similar issues.  Are there compiler options or other environmental options that can cause this? Has anyone nailed down the root cause? I would really appreciate any suggestions.

 

Thanks,

G. M.

Michael,

 

Thanks for the help. That thread does have some good info. I think my problem may be related to something like an ASP.NET 1.1 – 2.0 inheritance problem. My local test site where I don’t have any problems is basically a new DNN 4.5.1 installation whereas the host site was upgraded a couple of times. However, I still am unable to fix the error. One brute force option is to have them install a clean new DNN version 4.5.1 and then see if I can install my module there. If it works then I’ll try to figure out how to clean up the actual sites where I want to use it.

 

The thread you provided did suggest compiling with “Allow precompiled site to be updateable” unchecked as one fix. However that basically just provides a dll. Rick Strahl refers to this as a full pre-compile (all the user controls, code beside, etc. get compiled into the dll) in a CoDe Magazine article on ASP.NET 2.0 deployment. Can you do that with a DNN module? It seems that DNN expects the basic View, Edit, and Settings controls to be installed as ascx files. Correct?

 

G. M.

Thanks Michael,

 

I’ll check out the DNN dll possibility. I have a couple more brute force approaches also. I think I may just download a backup copy of the site from my hosting server and see if I get the same error if I set it up locally. That should tell me something. In theory the hosting site is pretty much the same ASP.NET 2.0 environment except I am running under Win XP Pro with IIS 5.1. I think they are running Win 2003 and IIS 6.0.

 

I don’t use WAP. I was under the impression that method was primarily to be used for converting old apps originally developed under VS 2003. What is WSP? I call what I do WDP (Web Deployment Project) with partial compilation, i.e. all the VB code is compiled into the dll but the ascx files, etc. remain separate and are compiled by the ASP.NET 2.0 JIT compiler.

 

Also I am using that dynamic placeholder with this particular module. Are you aware of any possible BC30456 error problems with that control? It works great in my local environment.

 

I’ll post whatever results I get here. Of course I am assuming I’ll get this solved! However, at this point I expect no holiday weekend for me!