HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Major Host/Test environment Compile problems (Error BC30456)Major Host/Test environment Compile problems (Error BC30456)
Previous
 
Next
New Post
5/26/2007 9:36 AM
 
Thanks for all the help Michael. Using the full source for my module does correct the problem. What also corrects the problem is to replace the DLLs in the /bin of the DNN installation that was set up with the DotNetNuke_04.05.01_Install.zip file with the recompiled (using VS2005) DLLs from the /bin of my DNN installation that was set up with the DotNetNuke_04.05.01_Source.zip. I am going with the full source (what you call the WSP model) installation of my module because I am not concerned about protecting any source. However, the DNN team should address this problem because others may not want to do that. Having to copy the recompiled DLLs into your /bin on your hosting system doesn’t seem like the best solution either. I have to say that I learned a lot out from this experience but it certainly wasn’t pain free! However I’ll look at the bright side. I didn’t end up working all weekend on this problem as I thought I would.
 
Thanks again for the help.
 
G. M.
 
New Post
5/26/2007 9:37 AM
 

I,ll assume that Tony will bring this to the attention of the DNN Team.

G. M.

 
New Post
6/13/2007 6:20 AM
 

I'm having a smiliar problem with a custom module built in VS2005.  When the "View" ascx page tries to reference "Me.ModulePath", the page throws up the BC30456 error and says "ModulePath" is not a member of "... the page ascx ..."  This only happens in the Hosted environment running Win2k3, IIS 6.0.  On my development machine, it works just fine.

I am, however, using the WAP (Web Application Project) model because this code is to be re-distributed and needs to be pre-compiled.  So, I can't use either option mentioned previously (using WSP, or recompiling all the DNN dlls).  I used Vladin's "blank module" approach to get my module started.

Are there any other options for getting around this problem when compiling pre-built assemblies for distributing modules?

Thanks.

-- W.G.

 
New Post
6/13/2007 9:16 AM
 

I don't know of any other solutions. It seems that if the DNN packages were compiled with only VS2005 this problem would go away. That worked for me when I did it with the source code installation zip file. But maybe there is some other issue that I am not aware of that has an impact on this. I am not sure how the various dll files of the installation zip files get compiled or who does it. I think the DNN team is aware of this issue but you might want to check.

G.M.

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Major Host/Test environment Compile problems (Error BC30456)Major Host/Test environment Compile problems (Error BC30456)


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:

1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

DotNetNuke Scoop!

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.