Products

Solutions

Resources

Partners

Community

About

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!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.


Help Improve DotNetNuke 5.4.3 – How to Submit an SVN Patch

Now that DotNetNuke 5.4.2 is out the door we are starting on the issues in the 5.4.3 Roadmap.  We have included quite a few community code submissions in the last couple of releases and we’d like to include more community code in 5.4.3.  You can submit your code fixes through Gemini as I detailed here, or you can also make use of the open repository we maintain at CodePlex and use SVN to submit a code patch.  I’ll show you how to do that in this post.  CodePlex will notify us that a patch has been submitted but it also a great idea to add a comment to the issue in Gemini as well so we can keep track of who is submitting code fixes.

If you have a code fix for an issue that is not in the roadmap submit it anyway and we may be able to triage it into the release.

 

To create a patch for SVN the first thing you need to do is pull the source from CodePlex.  You do this by using a tool such as Tortoise SVN which you can get for free here.

Once you have an SVN Client installed you need to get the source.  To do that simply right click your local folder and select “SVN Checkout”.  This will open the following dialog box.

image

To find out what the URL of the repository is you can go to the Source Code page of the DotNetNuke CodePlex site located here.  When you get there click the Connection instructions link to show the following:

image

Copy the Subversion URL into the Tortoise SVN dialog box.  Make sure you add /trunk to the end of the URL so your dialog box looks like this:

image

Now press OK and the source code will be pulled from CodePlex to your local machine.  Please be aware that for now the solution in CodePlex is for VS2010 only, the project files are all modified for VS2010 and do not open VS2008.  You can open in VS2008 if you modify the project files yourself.  An easy way to do this is to grab the .VS2008.vbproj files from the released Source package and use the VS2008 solution file from the Source package as well.

Once you have downloaded the code you can open the solution and make your bug fixes.

Then comes the part where you create a patch with SVN.  Its really very simple.

Right click your source folder and select Create Patch from the SVN Menu

image

This will show you a dialog with all fo the files you changed for your fix.

image

Press ok to show the Next screen where you can save the patch.  Please use the Gemini issue number and your DotNetNuke username as the file name like so:

DNN-99999-philip.beadle.patch

image

The last step is you will be shown the actual patch file:

image

You can now either attach this file to the issue in Gemini

image

Or submit it as a patch to CodePlex

image

Please remember to be descriptive about your changes so we can review them easily.

 

Thanx for your valuable help with DotNetNuke.

Comments

Comment Form

Only registered users may post comments.

NewsArchives


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Daniels (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out