Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Maximum ASP
  Need Help?  
Professional technical support for DotNetNuke is available from DotNetNuke Corporation.
 


  Ads  
 


  Sponsors  

Meet Our Sponsors

AspDotNetStoreFront - E-Commerce by Design - The Leading ASP.NET shopping cart platform for developers!
Click here to go to dev.live.com for Windows Live developer resources
SteadyRain
DataSprings - Great Ideas. Always Flowing.
R2integrated - formerly bi4ce
Jango Studios - Skins, Modules and Hosting for DotNetNuke
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Extend It! ( Pr...  References are making me cross-eyed!
Previous Previous
 
Next Next
New Post 2/28/2006 11:01 AM
User is offline David Bolling
12 posts
10th Ranked


References are making me cross-eyed! 

I had a custom module set up within the "Desktop Modules" solution provided with DNN.  I was able to set breakpoints in my module and things were fine.  I needed to put my module in Source Safe, but didn't want to put the DNN stuff in Source Safe.  So, I had a cunning plan...

I made a project with just DNN, a build support project, and my two projects (main and sqlprovider).  In the build support, I set the output directory to the /bin folder of DNN, referenced the two module projects, and set CopyLocal to "TRUE" for each reference.  In the two custom projects, I referenced the DNN project and set CopyLocal to "FALSE" for each project.  I then added my two modules to Source Control, and everything compiled and seemed to run just fine.  I opted not to build DNN in the Config Manager.

I was quite proud of myself, as I must have finally understood how everything relates.  That was until I needed to debug something in one of my custom modules.  I set a breakpoint in my main module, and nothing happened.  Everythng was set to compile in debug mode, so that wasn't it.  I went back to the DesktopModules solution that was working, and it seemed to work fine...  Although somehow I was writing files to my VSWebCache folder in My Documents.  I had run into this before, but deleting the webcache folder cured it then.  Not now, evidently.  Also, when I put a breakpoint in DNN in ModuleSettings, I think, and as I stepped through, I ended up in a VB file that was not being used at the moment, but had at one point been referenced via an "imports" statement from the module I wanted to debug.

That told me that somehow, my dlls were not stacking up right, or that the proper projects were not looking at each other right.

If I only had four projects in a solution, how should they reference each other so I can step through my code in the module?  The four projects are DNN, BuildSupport, my main module project, and my sqlprovider module project.  I must have done it with blind luck the first time.  And what's up with the VSCache?  Anyone know what happens to cause that?

Thanks,

Davey Bolling

 

 
New Post 3/2/2006 5:18 AM
User is offline Crispy
3370 posts
www.apptheory.com
4th Ranked










Re: References are making me cross-eyed! 

As for the VSCache, this only happens to webprojects and can be avoided if you turn all your webprojects into local project. This requires you also setting the default.aspx page and its web path manually in your build settings for DotNetNuke project itself and that it be the startup project as well.

As for module projects and references I do the following:

Build DotNetNuke.All

Add DotNetNuke project to my solution.

Add my CustomMod project to my solution.

Add my CustomMod.DataProvider Project to my solution.

Add a new build support project (located in my custom mod folder) which references my CustomMod.DataProvider project and set its build path to the root\bin. This will bring over the CustomMod reference as well at build time because of the DP's dependance on it.

All projects in this master project solution and their references should be project references if the project is part of this solution. All controls references that are actually in the controls folder should be referenced via DLL's in the respective controls\ folder.

All these should build to their own bin's to avoid conflict.

 



 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Extend It! ( Pr...  References are making me cross-eyed!
 


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.

 


Code Endeavors, LLC
Do you Endeavor to Enhance your DotNetNuke designs by utilizing AJAX technologies to more efficient interactive web experiences
www.codeendeavors.com
T-WORX, INC.
Professional DotNetNuke Solutions
www.t-worx.com
AppTheory
Professional development for medium to large projects based on the DotNetNuke platform.
www.apptheory.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP