Repository navigation
v1.8.3
DNN Manager 1.8.3
Keep DNN's upgrade path up to date yourself. When DNN lists a new version on its upgrade path, you add it in Settings, without waiting for a new DNN Manager. A project made from a live site's backup also no longer ends with a QUOTED_IDENTIFIER error.
Highlights
DNN's upgrade path, in your hands
- Settings → DNN releases → Edit upgrade path… lists the whole path DNN Manager knows, newest first, with the .NET Framework and SQL Server each version needs.
- Add version adds one DNN lists later, and Upgrade DNN then stops at it on the way. Type it as
10.4.2or as DNN writes it,10.04.02. - Needs .NET Framework and Needs SQL Server hold for that version and every one after it: a site that doesn't have what it needs is blocked before anything changes. The SQL Server list goes past 2025, for versions that don't exist yet.
- Note in the upgrade plan puts what to look out for on that step of the plan.
- Versions can only be added and minimums only raised. DNN Manager's own stops stay, so nothing you type can skip a stop or lower a minimum.
- A version DNN never released stops the upgrade before it starts, with nothing changed, and says it was added in Settings. The plan says when a step is one you added, which DNN Manager has no tests of.
- A new release that isn't a stop needs nothing: Upgrade DNN… offers it as it did, as a last step with a warning.
A live site's backup, restored without an error
- Making a project from a live site's backup - Import with a zip and a
.bacpac, Host project with a backup, or a clone - could end with UPDATE failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER' on the Output tab. - The site was made, but its pages marked secure stayed marked, and the operation ended with an error. That step now works, and so does everything else DNN Manager runs in the SQL container.
Other changes
- Fixed: a site that takes longer than 15 seconds to answer after it is set up showed a timeout message from
HttpClient. It now says the first start can take a few minutes.
Upgrading
Install over 1.8.2 as usual. Your settings keep their format.
- A site restored before this version, with the error above, may still have a page marked secure. Restoring it again clears it.
Tested
- The statement that failed, on a real site's database restored from a
.bacpac: without the fix it fails with the error above, with it the update goes through. That test was rolled back, so the database wasn't changed. - On a SQL Server container of its own, turning a site's SSL off on a table with a filtered index, as DNN's pages have: it passes with the fix and fails with the same error without it.
- The upgrade path compared with DNN's own page on 30 October 2026, one step at a time: all 17 steps are the same. DNN's page lists nothing past 10.03.03 yet, so DNN 10.4.1 is a last step past the path.
- All 472 fast automated tests pass, up from 442. New ones cover versions added to the path, minimums holding from their version on and never lowering what is known, the rules for what can be added, keeping them across a restart, the upgrade path dialog, and the first-start message.
Full list of changes: CHANGELOG.md
SHA-256
1e0f89dba0307e4c2d34bf4d4561d8f38bfdbac8ba2a0de80e62a4d6d3d6e908 DnnManager_Portable-1.8.3-x64.exe
37f69599e1ae3136dadb27a3a2b3c7a6d8af01108550ef99b7c09dd88d095724 DnnManager_Setup-1.8.3-x64.exe