Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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.0Modify a core module v3 in DNN 4.5.5 with VS.2005?Modify a core module v3 in DNN 4.5.5 with VS.2005?
Previous
 
Next
New Post
9/3/2007 4:24 PM
 
cendion

Joined: 5/19/2007
Posts: 7

Three question in one...:

I have DNN 4.5.5 source version installed on my dev machine using VS.2005 Sp1 and SQL Server 2005 (running on Vista). The installation is working and I've managed to skin it nicely.

I would now like to customize one of the core modules so it better fits our requirements (preferably without destroying the original one, how?). Why? Well, my initial wish was to have a content manager logging in and updating the company news himself. Easy, I thought, there just got to be a News or Article module of some kind that does this (as this IS pretty common in all CMS). I was dead wrong, the News module just handles RSS and the Announcements module is to clumsy for this as it requires separate pages to be created as well and it's too much work for the content manager.

Ok, if I use the Blog module I come pretty close to my wishes, espescially if I modify it a little. My problem now is:
How do I modify the Blog module that is in DNN version 3 format with my installed and already slightly modified DNN 4.5.5 source version on my VS.2005 installation?

This I haven't figured out yet despite extensive reading in the forums.

Also, what is and do I need to use this WAP model I keep reading about in VS.2005? (Observe, I AM using the VS.2005 SP1 which supposedly installs this).

 

The last thing I struggle with regarding DNN is if it is possible to send data between modules in some easy way? I think this is done in the blog module but I don´t know how? Shouldn´t there be an easy way to do this? I would like to show all my blog posts in a list and when a specific blog post is clicked upon, it should show up in another module in a pane beside the list (so it all shows at the same time), like this:

blog post
blog post --> (clicked on) --> Post shows up
blog post
blog post
aso..

Is the Inter-Module Communication (IMC) the (only) way to go - or is that overkill?

/Thanks (bear with me, I'm quite new on VS.2005 and ASP.NET, been working with PHP before but now trying to understand the DNN framework)
 
New Post
9/4/2007 12:10 AM
 
Chris Paterra


Joined: 4/5/2003
Posts: 4377

I would honestly look for another module that is a better fit. You could probably use Scott M's news articles module. It is a subscription based site located at: www.ventrian.com.

If you still wish to work on the blog module and its still built using vs 2003 (I am not sure), you will need to upgrade the module with visual studio.

The WAP mention is a compiled module built in a format similar to that used in VS 2003. In VS 2005 the compilation model was changed, and later a service pack (SP 1 for VS 2005) was released to accomdate developers comfortable with WAP structure. (Like myself)

As for you last question, IMC can work but may not be necessary. The blog populates most of its data based on querystring parameters. You can use these same parameters to control the behavior of your custom module instead of working with IMC. The direction you take depends really on your preference and your requirements.

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
9/4/2007 2:30 AM
 
cendion

Joined: 5/19/2007
Posts: 7

 

Hi, thanks for your reply. I know there's a lot of premium modules I can buy, but my intention is to learn how to develop my own modules (by first dissecting and modifying others). One of the reasons why I choosed the Blog module is that it already uses some kind of inter-module communication it seems, and that is what I would like to accomplish.

I've done some searching on upgrading a dotnetnuke module from v3 to v4 in visual studio but haven´t found anything. I will keep on looking (as I'm pretty new to VS.2005). If anyone has some tips on this matter, feel free to contribute.

Regarding WAP, I was also wondering if WAP is a *requirement* to develop (or customize) modules? I don´t think so but it would be nice to know for sure.

And for my last question you write that IMC can work but may not be necessary?! Interessting, it seems I have to dig on further on this issue. My only intent is that when a user has clicked on a blog post in the blog, the specific blog message should come up in another "place" on my side - while keeping the blog visible. If that other place is (or must be) in another module - then I thought I HAD to use IMC. I know I can show my blog posts with for example the UDT, but the problem is "how to show that blog post that the user clicked on in another module?". For this I have to pass the object ref in the parameters in some way, and then catch it in the recieving end.
 
New Post
9/4/2007 8:57 AM
 
Craig Walker


medfluent.net
Joined: 7/12/2004
Posts: 240

Here are some pages that may help...

DNN WAP Setup
http://www.netqconsulting.com/Tutorials/DNNWebApplicationProject/tabid/126/Default.aspx

IMC Example
http://www.netqconsulting.com/CodeSamples/IMCInterModuleCommunication/tabid/128/Default.aspx

Since you are already running VS2005 SP1, you should be able to skip the VisualStudio updates part (first two downloads).  MSBuild and DNN WAP still apply.  You should be aware the DNN WAP templates were developed some time ago and core architecture has since been enhanced.  For normal module development, you won't notice anything.  When you start building your PA scripts, though, you'll notice there are a few columns missing in the template.  For example, the script to create/register the module is missing the flags for Partial Rendering Suppport, etc.  Don't let that deter you; it's just a heads up.

As for what you are trying to do, I agree with Crispy that the Blog module is probably not the one you should use as your reference and IMC is probably overkill.  I also can't state clearly enough the importance of NOT editing a core module without really thinking through the ramifications.  Editing a core module will break it forever more and you'll miss out on all the great enhancements.  I do, however, support digging into the core modules in a development or test environment to learn how they tick and to pick up a few tricks.  Ultimately, you'll want to start with a blank module and build your own.  Trying to make a copy of an existing module and editing it without affecting the original almost always results in naming conflicts of some kind.  Surely... I digress.

On the IMC question, I don't really see why what you want to do needs to be two modules.  I would create one module that has a navigation section and a detail section.  You can use ajax to make it rich and responsive and you can use something like ComponentArt Snap if you want to be able to move your nav panel around.  If I understand your desired outcome correctly, this really seems like a pretty simple (and useful!) module, but I would just put it all together and stay away from the complexity of something like the blogs.
 
New Post
9/4/2007 4:38 PM
 
Néstor Sánchez


www.nestorsanchez.net
Joined: 11/15/2003
Posts: 1986

cendion wrote

I've done some searching on upgrading a dotnetnuke module from v3 to v4 in visual studio but haven´t found anything. I will keep on looking (as I'm pretty new to VS.2005). If anyone has some tips on this matter, feel free to contribute.

 

Moving DNN 3 modules to work as DNN 4 WAP modules

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Modify a core module v3 in DNN 4.5.5 with VS.2005?Modify a core module v3 in DNN 4.5.5 with VS.2005?


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