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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositorySetting up the Repository Module for Debug, HELP!Setting up the Repository Module for Debug, HELP!
Previous
 
Next
New Post
1/25/2007 6:02 PM
 

I have setup a development environment using DNN 4.4.0 following the "not using IIS" method described on http://www.adefwebserver.com/DotNetNukeHELP/ and the environment is working great for new module development. 

My question/problem, is I would like to load in the source for the repository module so I can make some modifications.  I have downloaded the source from the projects area, but for the life of me I have no idea how to get it setup in my environment to be able to debug and make modifications.  I am new to module creation and would greatly appreciate any advice on how to set this up.  Can someone give me a step by step on where the files need to be located and what I need to do to get it so I can step through the code in debug mode?  Can I do this in version 4.4.0 or do I need to use 3.3.7?  I don't really care what version as long as I can modify the code and debug it.

Thank you in advance,

Dan

 
New Post
1/25/2007 9:41 PM
 

The Repository is a .NET 1.1/VS2003 project so ideally using VS2003 would be the best way to go about making changes to the code (so yes, DNN 3.3.7). If you don't have VS2003 and only have a newer version of Visual Studio then you could try the Module Upgrade Wizard on the Downloads page.

 
New Post
1/25/2007 11:42 PM
 

You're not restricted to a specific version of DNN. You can use both VS 2005 or VS 2003. In either version, you will have to fix some function calls which have been made obsolete since the module was last compiled.
To get it to work I would do the following:
a) Create a folder which has your DNN source code (whatever version)
b) Create another folder in which you drop the source for the Repository module (I typically do this whenever I work against any module).
c) Open VS 2005 or VS 2003 and right click the solution to add existing project. Point this to the project file for your Repository source that you unzipped in step b. (in VS 2005, you will be asked if you want to upgrade the project to 2005, say yes)..
d) Open the properties page for the Repository project and point the build folder to be the bin folder of your DotNetNuke site.
e) Attempt to build the Repository module and you should get errors about obsolete methods, etc. Go through the list and fix them. Most of them are easy to fix but let us know here if you are stumped by any.

At this point you should be able to build and debug the repository module (after making the changes from step e).

Please note that these steps assume that you've already installed DNN and also the Repository module via the front end. If you haven't then make sure to do that before attempting to debug, etc....

Let me know if you have any questions...

Sanjay


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
1/26/2007 10:07 AM
 

Sanjay,

Thank you for your detailed response it has gotten me closer than any other response I have gotten elsewhere.  I do have several questions.

1) In the Repository source it has three project files (DotNetNuke.Modules.Repository.vbproj, BuildSupport.vbproj, and DotNetNuke.Modules.Repository.SqlDataProvider.vbproj) as well as a solution file DotNetNuke.Repository.sln.  I followed your steps for the DotNetNuke.Modules.Repository.vbproj it converted well, as far as I could tell.  It did give a conversion warning

Conversion Issues - D:\mySource\DNN\Repository\DotNetNuke.Modules.Repository.vbproj:
MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please remove the reference to project http://localhost/DotNetNuke/DotNetNuke.vbproj and add it again.

So my first question is should I be adding all three of the project files to my dotnetnuke website (I'm using VS2005) or should I be doing something with the solution file?  If I am heading in the right direction how do I resolve the conversion issue or is this not a big deal?  The first 102 errors I have are all Type <name> is not defined or Name <name> not declared.  So I'm assuming I am missing some key files/references.

Thanks again for all your help you have already gotten me significantly further than I expected to get on my first pass.

Dan

 
New Post
2/6/2007 5:29 PM
 
wardda wrote

Sanjay,

Thank you for your detailed response it has gotten me closer than any other response I have gotten elsewhere.  I do have several questions.

1) In the Repository source it has three project files (DotNetNuke.Modules.Repository.vbproj, BuildSupport.vbproj, and DotNetNuke.Modules.Repository.SqlDataProvider.vbproj) as well as a solution file DotNetNuke.Repository.sln.  I followed your steps for the DotNetNuke.Modules.Repository.vbproj it converted well, as far as I could tell.  It did give a conversion warning

Conversion Issues - D:\mySource\DNN\Repository\DotNetNuke.Modules.Repository.vbproj:
MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please remove the reference to project http://localhost/DotNetNuke/DotNetNuke.vbproj and add it again.

So my first question is should I be adding all three of the project files to my dotnetnuke website (I'm using VS2005) or should I be doing something with the solution file?  If I am heading in the right direction how do I resolve the conversion issue or is this not a big deal?  The first 102 errors I have are all Type is not defined or Name not declared.  So I'm assuming I am missing some key files/references.

Thanks again for all your help you have already gotten me significantly further than I expected to get on my first pass.

Dan

Most of the errors should come precisely from references. The Build Support project shouldn't be needed anymore as you will reference dlls directly. Also unless you need your module to be portable to other DB systems, you may consolidate code from SQLDataProvider.vbproj.


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositorySetting up the Repository Module for Debug, HELP!Setting up the Repository Module for Debug, HELP!


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