Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Installing Module SourceInstalling Module Source
Previous
 
Next
New Post
8/19/2008 6:17 PM
 

Please bear with me...  Let's say I do want to work in the DotNetNuke source tree.  What directory would I unzip the module source files to?

 
New Post
8/19/2008 6:22 PM
 

You can either open the dotnetnuke.sln and add the links module as an existing project (i.e. essentially you follow the initial steps shown http://www.15seconds.com/issue/050505.htm ,but add an existing project rather than create a new one.), or else make sure the links module exists in desktopmodules/links

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/19/2008 7:12 PM
 

Thank you very much.  I have imported the DotNetNuke.Links project into the DotNetNuke_VS2008 solution.  When I build it, the missing assembly errors are gone.    There are still about 100 errors due to missing declarations, etc. though.  For example, "Null is not declared.  Null constant is no longer supported; use System.DBNull instead."  Is there some sort of dependency I need to define to make this build cleanly? 

Thanks for your patience.

Kevin

 
New Post
8/20/2008 8:19 AM
 

I can't say for sure as I'm not using a windows machine at the minute (I use linux in my dayjob), but typically the only references you have to add are the ones to dotnetnuke or else the webcontrols and webutility library. However that message you show "null is not..." is a warning, not an error, and can be safely ignored. As for the missing references messages, they should contain enough detail to let you know what assemblies must be referenced.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/20/2008 2:26 PM
 

Actually, these are not warnings, they are errors.  Including the one regarding 'Null is not declared....'.  And I see no information in the errors that indicate what assemblies might be missing.  For example, DataProvider.vb generates the error 'Name Framework is not declared.'  There is nothing beyond that.  What am I missing?

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Installing Module SourceInstalling Module Source


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out