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 ForumsBlogBloghelp with code-behind help with code-behind
Previous
 
Next
New Post
5/11/2008 5:31 PM
 

Hi all

i have been searching (i already went through the entire blog forum thread) and googling around for an answer. I am unable to make any changes with the source of the blog module.

I used the source zip when installing the new module; the blog modules works fine and i am able to see the code-behind files.

However, when i try to edit (or even delete) the code behind files, my changes are not reflected. i believe that this is since all the .ascx pages inherit the assemblies and do not look at the code-behind.

I am sure i am missing something, but can anyone give me any advice on how to start playing around with the blog module source, i have been stuck on this all weekend

Any help would be greatly appreciated

 
New Post
5/11/2008 7:43 PM
 

You'll have to not only make the changes you want to the code-behind files, but recompile the blog module to get a new "DotNetNuke.Modules.Blog.dll"

There should be a "DotNetNuke.Blog.vbproj" file hanging out with the other source-files.  You'de have to open this in Visual Studio, double check references and output paths...then make your changes as needed, recompiling as you make them..

 
New Post
5/11/2008 9:22 PM
 

Thanks, I will try that out and post back when it worked out for me.

One other quick question though, what did you mean by double checking references and output paths?

In either case i hope i will figure out.

Thanks again scott

 
New Post
5/12/2008 2:09 AM
 

Hi hurrymonkey,

the output path should already be set to the /bin folder, because your web app will look there for the needed assemblies. Moreover, your code files will probably rely on other assemblies (e.g. dotnetnuke.dll) that they need to find, references allow this link. I hope this answered your questions, if not, let us know.

Best regards,
Dario Rossa

 
New Post
5/12/2008 5:23 AM
 

hurrymonkey wrote

One other quick question though, what did you mean by double checking references and output paths?

I went ahead and loaded up the blog source to show you what I meant:

The Yellow "!" icons next to "Dotnetnuke" and "Dotnetnuke.Webutility" are references that need to be fixed.  Removing and re-adding should fix.

This particular problem is probably caused by the solution file looking for Dotnetnuke.vbproj in my DNN website folder.  At any rate, it's a common issue and good thing to check whenever your working on a source for the first time.

The solution file from the 3.4.0 Blog module I installed is also in VS 2003 (which is the version I decided to open it in).  Normally I would convert up to 2005 or 2008 before modifying a module like this, which usally isn't too painful.

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBloghelp with code-behind help with code-behind


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