DNN Community Blog

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.


Ensuring correct DNN version on module installation

It has been announced, that future versions of the module installer in DotNetNuke will introduce an additional option in the manifest (.dnn) file for compatibility requirements as minimum DotNetNuke version, required by the module. But this does not prevent  new module versions be installed on any previously published version. This can be a major problem, if the module requires a new version, that is not compatible with other installed modules and the SQL script already altered the database to work with the current module version only. So the new module version will not work and, as there is no downgrade skript, a reinstalled previous version will neither run. Uninstall is teh module definition no option, as all stored records of the module will be deleted. As a result, there are three survivor rules before an upgrade:

  1. back up your database
  2. check, if the backup did run
  3. check the prerequisites of the module

As we feared, that there are few users reading instructions and backups are somewhat non-sportive, we tried to find a solution, how to at least prevent the database from being updated, so the previous version can easily be re-installed. Therefore we extended the update SQL script:

We first compared the DNN version stored in the database with our requirements (DNN 3.3.0/4.1.0):

DECLARE @dnnVer INT
SET @dnnver = (SELECT TOP 1 Major*10000+Minor*100+Build FROM {databaseOwner}[{objectQualifier}Version] ORDER BY Major DESC, Minor DESC, Build DESC)
IF @dnnver < 30300 OR ( @dnnver >= 40000 AND @dnnver <40100)
        RAISERROR ('Incompatible DotNetNuke framework version installed. Please upgrade to V. 3.3 or V. 4.1 or re-install previous version of this module!', 16, 1)

Unfortunately the script is still executed after the raised error, so we have to repeat this check before every statement (and even a local variable gets deleted after each GO statement).

So we extended the script using a temporarily used table:

CREATE TABLE UDT_Install_Semaphore (value INT PRIMARY KEY)
GO

DECLARE @dnnVer INT
SET @dnnver = (SELECT TOP 1 Major*10000+Minor*100+Build FROM {databaseOwner}[{objectQualifier}Version] ORDER BY Major DESC, Minor DESC, Build DESC)
IF @dnnver < 30300 OR ( @dnnver >= 40000 AND @dnnver <40100)
    BEGIN
        INSERT INTO UDT_Install_Semaphore (value) VALUES (0)
        RAISERROR ('Incompatible DotNetNuke framework version installed. Please upgrade to V. 3.3 or V. 4.1 or re-install previous version of this module!', 16, 1)
    END
 ELSE
    INSERT INTO UDT_Install_Semaphore (value) VALUES (1)
GO

IF (SELECT value FROM UDT_Install_Semaphore) = 1
...
GO

IF (SELECT value FROM UDT_Install_Semaphore) = 1
...
GO

...

DROP TABLE UDT_Install_Semaphore
GO

This way, the user can safely re-install the previous version of the module. However he will need to re-run this script manually from host::sql menu, as the module version is updated regardless this error.

Comments

Comment Form

Only registered users may post comments.

NewsArchives


Aderson Oliveira (15)
Alec Whittington (11)
Alex Shirley (10)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (32)
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 (209)
Chris Paterra (55)
Clinton Patterson (40)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (154)
Dave Buckner (2)
David Poindexter (4)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (74)
Geoff Barlow (10)
George Alatrash (6)
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)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matthias Schlomann (15)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (28)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
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)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott S (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)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (2)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (165)
William Severance (5)

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out