As the title states, I'm currently attempting to update a site for a client from 7.2.6 to the latest in prep to move to an Umbraco Cloud instance.

So far I have tried to update from:

• 7.2.6 ~> 7.2.7 => Stuck at non-refreshing redirection screen
• 7.2.6 ~> 7.2.8 => Upgrade completes but no back office login page, white screen displayed with no errors in console
• 7.2.6 ~> 7.3.0 => Same as 7.2.8
• 7.2.6 ~> 7.4.0 => Upgrades, however, Nested Content properties are empty on content nodes in back office BUT front-end renders correctly
• 7.2.6 ~> 7.4.1 => Upgrades too, however still no Nested Content properties in content nodes AND front-end YSOD's as well with a null reference error on the Nested Content property (which I will fix when the upgrade is sorted!)
• 7.2.6 ~> 7.4.3 => Upgrades yet once again still no Nested Content in content node properties BUT front end worked again as Matt explained to me this evening:

"[...] the recommended approach we've suggested in the past is to first upgrade NC, then resave all nodes with NC on them so this will apply the auto fix to switch to doc type aliases, and then do the Umbraco upgrade."

Which I did!

So, can anyone please shed light on why each of these attempts to update the core has consistently fallen over and won't let me update the core AND keep the node properties and data types filled?

Please note that I have updated the ClientDependency version in the CD.config, or web.config, depending on where it was for that specific update; as well as cleared the browser cache to the beginning of time, deleted the /TEMP/ClientDependency directory for each attempted update, and rolled back the changes in both the Git Repo as well as via SQL Server Management Studio 2014 restore tool.

I'm really confused on what is causing these core errors on updates as well as why it seems to want to remove the NC properties from the content nodes in the back office when they've been updated to the correct value types in the DB?!?!

If it helps, when I originally received the files, it was explained that everything had been installed via zip files during the initial build process but I felt it was better to handle as much via NuGet as possible inside Visual Studio 2017.

I was able to overwrite the core instance via NuGet, as well as the following packages which have worked as version 7.2.6 runs fine in the browser and back office.

So, unless otherwise noted, these packages are now handled by NuGet - the first number is the initial version and the second is the current version:

• Angular Google Maps ~ v.1.0.7-alpha-000010 ~> 2.0.3
• Articulate~ v.1.0.9 <= NOT UPDATED YET
• CMS Import ~ v.3.1.1 <= REMOVED
• Config Tree ~ v.3.1.0 ~> 3.2.1
• Diplo Trace Log Viewer ~ v.2.1 ~> 2.3.2
• Full Text Search ~ v.6.1.2 <= NOT UPDATED YET
• Nested Content ~ v.0.1.1 ~> 0.4.0
• RJP.MultiUrlPicker ~ v.1.3.1 ~> 1.3.2
• Robot.txt Editor ~ v.3.0 <= LATEST ALREADY
• SearchEngine Sitemap ~ v. 0.0.1 <= NOT UPDATED YET
• SEO Visualiser ~ v.1.1.0 ~> 1.2.0
• Slimsy ~ v.1.1.5 ~> 1.1.5
• Umbraco Forms ~ v.4.1.4 ~> 4.4.3
• Url Tracker ~ v.3.8 ~> 3.10

If it hasn't been updated then there are issues with dependencies noted per package and will be handled asap.

I'm building in VS 2017 Community, git version 2.13.3.windows.1, SQL Server Express 2014, IIS version 10.0.10586.0, 64 Bit Windows 10, Dell XPS 17" i7 1.73Ghz with 16gb Ram

Any further clarifications or questions please ask and I will strive to answer as best I can!