New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...WAP Module not building to root binWAP Module not building to root bin
Previous
 
Next
New Post
8/21/2009 6:04 PM
 

I've searched for this pretty exhaustively, so I apologize if it's been answered.

I'm just learning how to develop custom modules, and everything is goin ok except for this:

When I right-click and "Build" my WAP(located within a DNN Source install DesktopModules folder), it refuses to spit the dlls into the root bin folder.  My output path is set as "..\...\bin\" but it will only put the dlls in the module's bin folder under DesktopModules.

I've set my project properties up to look exactly like the properties page from a DNN Compiled Module template(which compiles to the correct folder).   It is also compiling to an "obj/Debug" folder....but the Compiled Module template does this as well so I assume that it is normal.

I feel like there is some silly setting I've missed...any ideas?

PS - When I manually copy the DLLs into the correct bin the module works as it should...if that helps at all.

 
New Post
8/21/2009 8:30 PM
 

In the project properties - compile tab, note that the Build Output Path can be set to different paths depending on the Configuration drop down's value - Active, Debug, Release, All. Most likely, the path is set to build to \bin for the Debug and ..\..\bin\ for the Release configuration and your Active configuration is set to Debug for the project.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
8/24/2009 9:36 AM
 

Thank you for your reply...unfortunately this was not the problem.

I wasn't sure how to change the output path based on the build configuration, but I did build the product in the different configs so that if it was set for one of them and not another it would catch it.  But the problem still remains.

 
New Post
8/24/2009 10:04 AM
 

that is weird - not sure why this is happening - but you could try this as a workaround - create a PostBuild script which simply copies the dll over to the bin folder you want it in...
I'm not saying this is your "fix" but at least it'll get you past this problem (for now)....

Have you also confirmed that the "../../bin" is actually pointing back to the bin folder of the solution? ie did you select it from the list of folders or was it there from before? Sometimes I've seen some settings not "stick" in DNN and maybe if you cleared it out and reset it, it might work...

Sanjay

 


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
8/24/2009 10:05 AM
 

Aha!   I was cross referencing a couple different VSproj files and it turns out you were correct...One of the build configurations was not set for the correct file.  For some reason my Build Config was set for Mixed Platforms instead of AnyCPU so it wasn't really picking up any of them anyways.

Thanks for your help, you certainly pointed the right direction for me!

 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...WAP Module not building to root binWAP Module not building to root bin


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, 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 DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.