Skip to main content

DotNetNuke: Customized Events Module Upgrade to Standard

Today I was able to upgrade a customized Events module of the DNN (DotNetNuke) at the request of the client. After my suggestion the client wanted to have the latest updates and also gave an okay to drop the customization and use the standard events module.

What should have been an easy upgrade quickly turned into a nightmare; a nightmare which took all evening yesterday and the early morning today.

It turns out that the install wizard does not rollbacks all the things as is; especially the ones which were checked with IF Exists or IF NOT Exists SQL.

I believe the IF (NOT) Exists scenarios should actually turn on and off boolean values so that they can be passed on as parameters to the other SQL scripts and all the way to the rollback scenario.

It was really painful to redo all things at least ten times as the error was triggering the rollback and retry will fail at missing columns or columns already exists; which were added or deleted by the previous try and were not undone by the rollback.

  1. Table
    1. Events
      1. Remove index of IX_(objectQualifier)Events_4
      2. Add column PayPalPassword
      3. Alter Column name CreatedByID to CreatedBy
    2. EventsRecurMaster
      1. Remove all Relationship keys
    3. EventsSignups
      1. Add column TimeZoneOffset
  2. DLLs
    1. Delete all Events module related dlls (the dlls are locked and can't be overwritten)
  3. DesktopModules
    1. Delete the Events sub-folders and the Events folder as well. (resource files are locked and can't be overwritten)
At the end all things went fine but making it all work was painful and not an easy route.

Hope this can be helpful to any who are in similar situation as me.

 

Comments

Popular posts from this blog

Working hours in six months to a year

I usually try to look for how many hours I have worked on a given project and what hours that I  spend on learning or network management tasks.

Below I have added some hours calculation, after finding the breakdown by months from Berkeley website.


Credit: http://controller.berkeley.edu/payroll/payroll-system-pps/pps-training-materials/number-working-hours-month

2017Working hours six months (Jan 1st - Jun 30th): 
130 days x 8 hours =  1040 hours


Working hours six months (Jul 1st - Dec 31th): 
130 days x 8 hours =  1040 hours

Working hours for the year:
1040 hours + 1040 hours = 2080 hours
MonthWorking Days in the monthMonthly Working Hrs1/2 of working hrsMidpoint of working days in the monthDates of HolidaysJanuary22176888 a.m. 1/172,16February20160808 a.m. 2/1520March2318492Noon 3/1631April20160808 a.m. 4/17May2318492Noon 5/1629June22176888 a.m. 6/16July2116884Noon 7/174August2318492Noon 8/16September2116884Noon 9/154October22176888 a.m. 10/17November22176888 a.m. 11/1610,23,24December21168…

Completed UiPath - RPA Developer Advance Training

After a month of training, with late nights and weekends I have completed the UiPath RPA Developer Advance Training.

The Level 1 Foundation Training pretty much covered all the basics of Desktop studio and workflows, only draw back was I started with the default foundation course which was for 2016, and all document reference links where pointing to 2016 version. I didn't understand it during the foundation training and kept switching to 2018 version document/page.

Only after completing the Foundation course that I realized, I was suppose to have started with the 2018 version of Level 1 Foundation Training, but as it was optional I didn't have to retake the 2018 version, the 2016 was good enough for moving to level 2.

The Level 2 Orchestrator 2018.3 Training as good. It gave good understanding of Queue's, Jobs, and schedules and I was able to complete the level two much faster then the level 1.

The Level 3 UiPath Advanced Training was bit tough as it involved the assignme…