Sign In  |  Register
 
 
DotNetNuke Support Forums
Editing a 3rd party module
Last Post 22 May 2007 01:42 AM by markchannon. 2 Replies.
Printer Friendly
Sort:
PrevPrevNextNext
Please Register to post a reply.
Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.
AuthorMessages
markchannon
New Member
New Member
Send Private Message
Posts:23

--
17 May 2007 07:00 AM  

Hi John

Got 2 different questions:

1. I'm just about to start learning about creating modules for dotnetnuke. I've got visual studio 2005 and MSSQL2005 and I rent a windows 2003 server etc. From my searching it seems that there is a really good way of creating modules for DNN3 but DNN4 isn't quite there yet. Found this article on it:

http://quiziqal.com/blogs/icode/archive/2007/02/03/118.aspx

Do you have opinions on the best way to go about it or any examples tutorials?

2. There are a few 3rd party modules which I have the source for which I just want to tweak but I don't know where to start. Do I just open up the project in Visual Studio edit and then rebuild? Do I need to set something up so it references dotnetuke, if so how do I go about this?

My example is that I have a module which the currency is in $ and I want to change to £, so it should be really easy to change this but have to edit the source to do it, then rebuild. Any advice examples on this would be great as I will probably do this more than creating modules from scratch.

Thanks

Mark

John Mitchell
Administrator
Veteran Member
Veteran Member
Send Private Message
Posts:4392
Avatar

--
20 May 2007 11:50 AM  

Hi Mark,

Sorry for the delay in responding.

I think that link for using codesmith templates is a good place to start if you are building your own modules from scratch. 

Also read the DotNetNuke Module Development documentation in the download package and take advantage of Michael Washington's tutorials (he had responded in the comments of that post you gave a link to).

For #2. If the modules are dynamically compiled at run time you can make your changes to third party modules without even having to set them up in Visual Studio.  If they are not, then you should have a project file delivered with your source of the module (if not ask them to provide one).

After using the project file, you may need to correct references that are different from their environment as compared to yours.  If you run into any of these that you can't get corrected then feel free to ask here on how to resolve them.

Developing in ASP.Net is very rewarding, but there is a learning curve much higher than that in a scripting language like classic ASP or PHP.

To get a good understanding of the basics I would recommend the videos at http://www.learnvisualstudio.net/

There are also some DotNetNuke module development videos that may help at http://www.dotnetnuke.com/About/TrainingVideos/tabid/810/Default.aspx

 

markchannon
New Member
New Member
Send Private Message
Posts:23

--
22 May 2007 01:42 AM  
Thanks John

I'll look into these!
Please Register to post a reply.
Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.


Active Forums 4.1
Visit our Store for great DotNetNuke Modules and Skins
DotNetNuke CSS Menu 3.4.6 (single use)

Item codeCSSNM33SU
AuthorJohn Mitchell
Base Price$39.00
Product Information 
DotNetNuke CSS NavMenu 3.4.6 (Developers)

Item codeCSSNM33DEV
Base Price$149.00
Product Information 
DotNetNuke Performance Caching & Compression - PageBlaster 3.4.5 - Professional Edition

AuthorJohn Mitchell
Base Price$59.00
Product Information