Skip to content

Releases

2.0.0-rc3

2.0.0-rc3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Nov 14:28

DNN Manager 2.0.0-rc3

Opens on a Mac, with its icon on Windows. The macOS app no longer says it is damaged, the Windows app shows the
DNN Manager icon everywhere, and lists and selects work from the keyboard. This is a release candidate: try it next
to your current version before 2.0.0.

Highlights

The Mac app opens

  • A DNN Manager downloaded from this release no longer says it "is damaged and can't be opened".
  • The first time, macOS says it can't check DNN Manager: choose Done, then System Settings → Privacy &
    Security → Open Anyway
    . After that it opens as usual.

The DNN Manager icon on Windows

  • The window, the taskbar, the desktop shortcut and Explorer show the DNN Manager icon instead of Windows' blank
    program icon.

Selects and lists from the keyboard

  • In a select, Up, Down, Home, End, Page Up and Page Down move the highlight, Enter or
    Space chooses, and Esc closes the list without closing the dialog. The list opens on the current value and
    closes when you click outside it. This holds for every select, Settings included.
  • Scroll bars can be dragged, or clicked beside the thumb to jump there; the thumb widens under the mouse.

Other changes

  • On Windows, Browse… for the Site .zip and the Database .bacpac in New project, and Import… in
    Edit DNN upgrade path, list only files of that type.
  • With the side bar closed, the page keeps its gap next to the activity bar.

Upgrading

Install the new package over the old one: the .msi on Windows, the .dmg on macOS, the .deb on Linux. Your settings
keep their format.

  • This is a pre-release: Check for Updates… doesn't offer it - download it from this release's page.
  • On a Mac where 2.0.0-rc2 was called damaged: drag this version to Applications over it and open it as above.

Tested

  • All 833 automated tests pass on Windows, up from 819; the build, the tests and clippy also pass on Linux and
    macOS.
  • The Windows app was built and its icon read back from DnnManager.exe.
  • Not checked yet: the signed app on a real Mac (the release builds it), and the keyboard in selects by hand.

2.0.0-rc2

2.0.0-rc2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Nov 19:38

DNN Manager 2.0.0-rc2

DNN Manager, rebuilt and installable everywhere. The whole app is rewritten in Rust with the pages and actions
you know from 1.8.7, and every release now comes as an installer for Windows, macOS and Linux. This is a release
candidate: try it next to your current version before 2.0.0.

Highlights

The app you know, rebuilt

  • Projects, a project's details, New project, Settings and Troubleshoot work as in 1.8.7: start, stop
    and restart sites, keep them warm, clone, back up, restore, upgrade DNN, rename, edit host names and app pools,
    change the database connection, and remove a site.
  • The bottom panel keeps Output, Logs and Terminal; the command palette (Ctrl+Shift+P), the guided
    tour and Help (F1) are there too.
  • Settings → Keyboard shortcuts lets you change the shortcut of any command.

An installer for every system

  • Windows: DnnManager-windows-x86_64.msi and DnnManager-windows-arm64.msi.
  • macOS: DnnManager-macos-arm64.dmg (Apple Silicon) and DnnManager-macos-x86_64.dmg (Intel) - open it and drag
    DNN Manager to Applications.
  • Linux: DnnManager-linux-amd64.deb and DnnManager-linux-arm64.deb (also as -x86_64.deb and -aarch64.deb), for
    Ubuntu 22.04, Debian 12, Linux Mint 21 or newer. apt installs what it needs.
  • IIS exists only on Windows: on macOS and Linux the app opens and says there are no websites to manage there.
  • SHA256SUMS.txt lists each file's checksum. The installers aren't code-signed yet, so Windows and macOS ask before
    the first start.

Your settings and projects carry over

  • DNN Manager keeps using Documents\DnnManager: your settings, projects, kept DNN packages, backups and logs are
    where they were.

Other changes

  • Check for Updates… (the gear menu) tells you when a newer release is out; you install it by downloading its
    package from the release page.
  • Esc closes a dialog from any of its fields; in a search box it first empties the search.

Upgrading

This is a pre-release: Check for Updates… doesn't offer it - download it from this release's page.

  • Source Control from 2.0.0-rc1 - with its Explorer, Search and tabs - isn't in this version. If you use it, keep
    2.0.0-rc1.
  • On Windows the .msi installs into Program Files\DNN Manager, next to a DNN Manager installed with the earlier
    Setup (Program Files\DnnManager) rather than over it. Uninstall the old one in Windows' Apps settings if you
    want only this one. Only one of them runs at a time.
  • DNN Manager no longer installs updates itself: install each new release's package over this one.
  • If DNN Manager started when you sign in, turn Start DNN Manager when you sign in to your computer on again in
    Settings → General, so it starts this version.

Tested

  • All 819 automated tests pass on Windows. They cover every action against stand-ins for IIS, SQL Server and the
    files, so nothing on the PC changes while they run.
  • Checked by hand on Windows 11 against a stand-in IIS: Projects, a project's details with its database read,
    New project with the DNN versions from GitHub, Settings, Troubleshoot, the menus, the tour, help and
    Check for Updates…. Reading a real IIS was checked once.
  • The Windows x64 .msi was built and holds DnnManager.exe for Program Files\DNN Manager.
  • Not checked yet - what this release candidate is for: actions that change a real site or database (create, clone,
    back up, restore, upgrade, rename, remove), the Windows ARM64 installer, and the macOS and Linux apps on a real Mac
    or Linux PC.

v2.0.0-rc1

v2.0.0-rc1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Nov 15:15

DNN Manager 2.0.0-rc1

Push and pull your sites, also on macOS and Linux. A new Source Control page compares your projects with their servers over SFTP, FTPS or FTP and pushes or pulls only the files you choose, after a review. It runs on Windows in DNN Manager, and on macOS and Linux in a new app. This is a release candidate: try it before 2.0.0.

Highlights

Source Control: deploy to a server, like git

  • Source Control in the activity bar (Ctrl+3) connects a project to its development, staging and production servers over SFTP (password or private key), FTPS or FTP.
  • A server is set up as in FileZilla's Site Manager: the same protocols, encryptions and logon types, in the same words. An Azure App Service connects as it does in FileZilla.
  • A server compares the files with the content they last agreed on. A file changed here is yours to push, one changed on the server is yours to pull, and one changed on both sides is a conflict. Which clock is later never decides it.
  • Each change has its diff, side by side or in one column. Stage the files you want, write a message, then push or pull only those, after a review of every file.
  • Nothing is overwritten unseen. A file changed since the comparison stops the push or pull before anything changes. A push that fails or is cancelled puts back what it sent.
  • Every push and pull is kept in the history, with each file before and after, and can be rolled back.
  • Secrets and each environment's own configuration (web.config, App_Data, keys) are left out, or asked about before they are sent.

Choose what to compare

  • Opening Source Control reads nothing from a server. Choosing a server compares it, and Ctrl+click or Shift+click compares several, one after the other.
  • CHANGES shows one server at a time, with its name beside the title to switch.
  • A server can have its own Local folder, with Browse…, instead of the project's folder.
  • Settings → Source Control sets whether the page compares by itself when it opens, how long the history keeps file versions, and what a new server starts with.

Explorer, Search and tabs

  • Icons at the top of Source Control's side bar switch between Source Control (Ctrl+Shift+G), an Explorer (Ctrl+Shift+E) of the project's files as a push sees them, and Search (Ctrl+Shift+F).
  • Search can match case, whole words or a regular expression. Replace all shows what it will write and asks first, then keeps each file's encoding and line endings.
  • Open files have tabs. Drag a tab to another place, or move the chosen one with Ctrl+Shift+PageUp / PageDown.
  • Select a diff's code and copy it with Ctrl+C or the right-click menu. Unified, Side by side and Whole file are icon toggles.

A window laid out as VS Code's

  • The sidebar is now the activity bar: the pages as icons, with their names as tooltips.
  • Beside it, the primary side bar holds a page's own view (Ctrl+B hides or shows it). The secondary side bar opens with Ctrl+Alt+B.
  • Drag either side bar wider or narrower. DNN Manager keeps the widths between starts, and Customize Layout shows or hides each part.

DNN Manager on macOS and Linux

  • A new app runs Source Control on macOS (Apple Silicon and Intel), Linux (x64 and arm64) and Windows, with the same servers and history as the Windows app.
  • Explorer, Search, tabs, merging a conflict and the layout above are in DNN Manager for Windows only, for now. In the new app you keep the project's or the server's version of a conflict.
  • Making and running DNN sites needs IIS, which only Windows has. Those pages say so, and suggest DNN Manager in a Windows virtual machine.
  • On macOS and Linux, saved passwords are encrypted with a key that only your account can read.
  • The release has a package for each: DnnManager-2.0.0-rc1-macos-arm64.zip, -macos-x64.zip, -linux-x64.tar.gz and -linux-arm64.tar.gz.
  • The macOS app isn't notarized by Apple. The first time, right-click DNN Manager and choose Open. On recent macOS, use System Settings → Privacy & Security → Open Anyway.

Other changes

  • Viewing files in Source Control reuses one connection to the server, reads each file once and reads the next few ahead, so files open quickly.
  • A group's title in the changes list folds it with one click, and stays at the top while you scroll.
  • The .gitignore written into a new site no longer leaves out files the site needs (DNN's js/Debug, bin/x64, install packages, 2sxc apps, portal themes). It now leaves out the site's web.config and its copies, database backups and .env files. Existing sites keep theirs.
  • Fixed: a diff's selection was drawn a few characters off from its text.

Upgrading

This is a pre-release. The Update button doesn't offer it: download it from this release's page. Install it over 1.8.x as usual. Your settings are kept, with a new Source Control section.

  • When 2.0.0 is out, Update offers it to you.
  • The portable exe is now named DnnManager-2.0.0-rc1-x64.exe, without _Portable. A portable DNN Manager you already have keeps its file name when it updates.
  • On macOS and Linux, unpack the package and start DNN Manager. Projects go in ~/DNN unless you choose another folder, and Settings → About shows where the app keeps its data.

Tested

  • All 587 fast automated tests pass, up from 498 in 1.8.7. New ones cover Source Control against a folder standing in for the server: comparing, pushing and pulling, conflicts and merges, retries and resumed uploads, rollback, and pushes that fail or are cancelled.
  • The new app's 4 automated tests pass on Windows. They cover choosing a server, which compares it and shows a file's diff; adding a server with its own local folder; the macOS and Linux encryption of saved passwords; and the default projects folder.
  • The new app has not yet been run on a real Mac or Linux PC: this release candidate is for that.

Full list of changes: CHANGELOG.md

SHA-256

2a8f60a04567ce8d4419dfc10f66be561a0ff919597b608adaaff028c3a3d353  DnnManager-2.0.0-rc1-x64.exe
3bdf0b4bd6a13f7d8b7ad4498402a077a129a6ecf44d6258233b3afac308d040  DnnManager_Setup-2.0.0-rc1-x64.exe
15b4616575d7296eb627c60f158d1b59fe5cbea84061579d2e3aa0fd9f5bcb22  DnnManager-2.0.0-rc1-linux-arm64.tar.gz
ccd545740d2e6d94e5eac016e8026cbcafd3c00b36a9f42641690de299fdcea3  DnnManager-2.0.0-rc1-linux-x64.tar.gz
7e31ead22237c49641ad3dff27242bb41024286c5e213266ffd29cd5616a9a26  DnnManager-2.0.0-rc1-macos-arm64.zip
364bc89d4ea81d4c851a45c6a58302d08bdae81ff80af83725276f54579f7582  DnnManager-2.0.0-rc1-macos-x64.zip

v1.8.7

Choose a tag to compare

@github-actions github-actions released this 05 Nov 14:32

DNN Manager 1.8.7

Pick the host account again. On a site with more than one host account, Change host password… showed an empty Host account box. You pick the account from a list again, and the lists in every select mark the right item.

Highlights

Choose the host account in Change host password

  • On a site with more than one host account, the Host account box stayed empty: picking an account from its list didn't show it, so you couldn't tell which account would get the new password.
  • The box now shows the account you pick. It starts on the first host account in the site's database.
  • It is a plain list now, not a box to type in: it holds every host account in the site's database, and DNN Manager refuses any other name anyway.
  • When the site's database has no host account, the dialog says so: The site's database has no host account to change.

Select lists that mark the right item

  • The chosen item stays marked as chosen while the list is open. Before, it looked hovered when the list opened and only turned blue once the pointer moved to another item.
  • The hover follows the pointer and goes away when the pointer leaves the list. It used to stay on the last item the pointer passed.
  • The arrow keys still show which item they are on.
  • This applies to every select in DNN Manager, such as Version in New project, Upgrade to in Upgrade DNN… and UI scale in Settings.

Upgrading

Install over 1.8.6 as usual. Your settings keep their format.

Tested

  • Change host password with two host accounts, the dialog drawn off screen with the app's own styles, dark and light: the first account shows when it opens, the one picked shows in the box, and the box can't be typed in.
  • The select's list, in the same way: the chosen item stays marked as chosen, an item the pointer has left isn't marked as hovered, and the item the arrow keys are on is.
  • All 498 fast automated tests pass, as in 1.8.6.

Full list of changes: CHANGELOG.md

SHA-256

6ca1b715374523b0aba0b337aa7dfabc64dfb99e2af60ff0d5422c4be6780085  DnnManager_Portable-1.8.7-x64.exe
5ee7a4086245519c9e95e16ca39380ca96bcda5da6a22c15bf8dcc18f4f24c31  DnnManager_Setup-1.8.7-x64.exe

v1.8.6

Choose a tag to compare

@github-actions github-actions released this 05 Nov 11:06

DNN Manager 1.8.6

Imported sites, on your address. Choose the host name and port of a site you import, just as for a new one. A .bacpac from an Azure SQL database now imports instead of stopping with a SQL error.

Highlights

Choose the address of an imported site

  • New project → An existing site now shows the IIS card: the Host name and Port the site answers on.
  • It starts as <name>.dnndev.me on the port from Settings → Projects. Change either one, or type a domain of your own such as shop.test. It goes into the hosts file, so the site opens without internet.
  • It is checked as you type: an address that another IIS site already has is refused, and Import project waits until you choose another.
  • DNN's site alias in the imported database follows the address you chose, so the site loads there on the first visit.
  • When the import is done, the toast has Open site.
  • The IIS card now sits right under Project, for a new site as well as an imported one.

A .bacpac of a contained database imports

  • A database with users that have a password of their own, which an Azure SQL database often has, stopped the import with BACPAC import failed: CONTAINMENT = PARTIAL | WITH ROLLBACK IMMEDIATE; | END. Whatever the import had done was then undone.
  • DNN Manager now switches on SQL Server's contained database authentication for that server and imports again. The Output tab says so: switching on 'contained database authentication'.
  • When an import fails, the message now gives SQL Server's own error (for example Msg 12824, …), not the last lines of the script it was running.

Other changes

  • DNN Manager now runs on .NET 10.0.14, which fixes a security issue in .NET's Brotli decoder.
  • In the getting started guide, Host name and Port is now step 2 of the New project form, in the same order as the page.

Upgrading

Install over 1.8.5 as usual. Your settings keep their format.

  • Importing a contained database switches on contained database authentication on that SQL Server, and it stays on. It only matters for contained databases.

Tested

  • All 498 fast automated tests pass, up from 493. New ones cover an import on a chosen host name and port, an import without one keeping <name>.dnndev.me, a contained database recognised from SqlPackage's output, and the error message an import shows.

Full list of changes: CHANGELOG.md

SHA-256

a8e56d15ca05799a6472cc49888c2703057128280bb6424a2147f4a13ce7198a  DnnManager_Portable-1.8.6-x64.exe
45eaeff2da5f74bdf4b948097b4e5f90fc94719cffd4975e62f4dfc7acd66ca2  DnnManager_Setup-1.8.6-x64.exe

v1.8.5

Choose a tag to compare

@github-actions github-actions released this 03 Nov 16:31

DNN Manager 1.8.5

The whole upgrade path is yours. Change what any version of DNN's upgrade path needs, take a version off, and carry the path to another PC as a file. Host project is gone: websites come in through New project and Clone.

Highlights

Edit the whole DNN upgrade path

  • Settings → DNN releases → Edit upgrade path… shows every version of the path, newest first, as a row you can change - not only the versions you added.
  • Raise or lower what one of DNN's own versions needs (Needs .NET Framework, Needs SQL Server), or choose No new minimum. The tooltip of each list says what DNN's path has.
  • Give any version a Note in the upgrade plan, and take a version off the path with its delete button, so upgrades no longer stop at it. The versions of DNN's that are taken off are listed under the path.
  • Add version puts a new row at the top, and Reset to DNN Manager's path undoes every change.
  • The dialog is a window you can resize: make it bigger to see more versions at once, and the notes widen with it.
  • The upgrade plan says what is yours: a step to a version you added, one that skips a version you took off, and one whose minimums you changed each carry a warning, and none of them is shown as tested.

Take the upgrade path to another PC

  • Export… saves the path, as it is in the dialog, to a .json file.
  • Import… fills the dialog from such a file. Nothing changes until you click Save.
  • A version DNN Manager learned after the file was exported stays on the path.
  • A file that isn't an exported path, or has a version that can't be used, is refused with the reason, and the path stays as it was.

Host project is removed

  • The Host project page is gone, with its sidebar entry, its command in the command palette and Ctrl+3.
  • A website comes in through New project - A new site, or An existing site from a .zip of its files and its database backup - or through Clone… on a project's right-click menu.
  • To point a project at another database, use Change connection… on its Database tab. To put a missing database back, use Restore backup.

Other changes

  • While Update downloads a new version, a thin bar under the button fills up, and its tooltip gives the percentage.
  • Buttons such as Cancel, Close, Import… and the bulk actions above the Projects table have a quieter outline, like the table's. Text boxes, lists and check boxes keep theirs.

Upgrading

Install over 1.8.4 as usual. Your settings keep their format.

  • The versions you added to the upgrade path in 1.8.3 and 1.8.4 work as before: they only add to what DNN Manager knows. Change one in the dialog and save, and your values replace DNN's.
  • Projects you set up with Host project keep working. A website folder that is already on this PC but isn't in IIS can no longer be set up from DNN Manager: make a .zip of its files and a backup of its database, and use New project → Start from: An existing site.
  • The download bar shows from the next update on. Updating to this version still uses 1.8.4's Update button.

Tested

  • All 493 fast automated tests pass, up from 473. New ones cover the edited upgrade path (a version taken off is skipped and the step says so, a lower minimum replaces DNN's, a version added earlier still only raises), exporting and importing it, and files that are refused.

Full list of changes: CHANGELOG.md

SHA-256

1eb48de4a79e4ed39cfa8ddf7a0582b916b0919de53be45d52085b545e2779b3  DnnManager_Portable-1.8.5-x64.exe
c4cf87c2b9b6536236b383eef1a4731ac2e7a194ce9e90139c1e8ea5910d7021  DnnManager_Setup-1.8.5-x64.exe

v1.8.4

Choose a tag to compare

@github-actions github-actions released this 02 Nov 14:05

DNN Manager 1.8.4

A live site's database backs up again. A project made from a live site's backup could not be backed up or exported: the database export stopped with SQL71501. It now goes through.

Highlights

Backups and exports of a live site's database

  • A database restored from a live site keeps its host's user, such as __shop. Exporting it stopped with Error SQL71501: User: [__shop] has an unresolved reference to Login [__shop], and the backup was undone.
  • This stopped Export → Site and database (.zip + .bacpac) and Database (.bacpac), Export → For deployment…, and the backup Upgrade DNN… makes before each step.
  • A .bacpac holds the login of every user in the database, and the site's own login (dnn_shop) sees no login but its own. A database on the local SQL Server container is now exported as the container's user (sa by default), which sees them all.
  • A database on another server is still exported with the login its web.config names. When that login can't see one of the database's logins, the error now says what to do: export as a sysadmin (or a login with VIEW ANY DEFINITION), or drop that user if the site doesn't use it.

Upgrading

Install over 1.8.3 as usual. Your settings keep their format.

  • A .bacpac exported from the SQL container now also holds the logins of the host's users, such as __shop. Restoring it on another SQL Server makes those logins with a random password, as it already did for DNN Manager's own dnn_ logins.

Tested

  • A real site's database restored from a live site's backup, with the host's user __ceesboer: signed in as the site's own login, only sa and that login are visible, which is why the export failed. Exported as the container's sa, the export succeeds, and the .bacpac holds both logins and both users.
  • All 473 fast automated tests pass, up from 472. The new one checks which login an export signs in with: the container's user for a database on the container, and the web.config login for a database elsewhere.

Full list of changes: CHANGELOG.md

SHA-256

abefbaab73ae5b9ddbae86f3e55303dce14f23787ce9416efc127d35ac75a336  DnnManager_Portable-1.8.4-x64.exe
c25b95bd2224413d20b53193ec0d476982d446fa338971d0c9db7a1e265261a3  DnnManager_Setup-1.8.4-x64.exe

v1.8.3

Choose a tag to compare

@github-actions github-actions released this 30 Oct 15:44

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.2 or 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

v1.8.2

Choose a tag to compare

@github-actions github-actions released this 10 Oct 18:38

DNN Manager 1.8.2

Its administrator rights stay its own. Nothing you or another program can change - your settings, environment variables, Documents, a site's folder - can make DNN Manager run code or delete files as Administrator any more. Terminals run as you, Cancel stops what it started, also inside SQL Server, and the SQL container works again with Docker installed for your account only.

Highlights

Administrator rights only where they are needed

  • Setup installs into Program Files for all users and asks for administrator rights when it starts. An installation for your account only keeps updating where it is; Setup offers to move it.
  • The installed DNN Manager is started through DnnManager-launcher.exe, which leaves out the .NET variables that would make it load other code. Start DNN Manager when you sign in and Windows' administrator prompt both use it.
  • Start DNN Manager when you sign in needs an installation for all users. A sign-in task made for a per-user installation is removed at the next start, with a warning.
  • Uninstalling lists what stays - your Documents\DnnManager, the saved passwords, %ProgramData%\DnnManager, Docker's container and volume, your projects - and offers to remove your DNN Manager data. No is the default; Docker, your projects and IIS are never touched.
  • A terminal opened with + runs without administrator rights, with your own shells, profile and PATH.
  • New Administrator terminal (the arrow beside +) opens one with DNN Manager's rights when you need it: only shells installed for all users, without your profile scripts, titled Administrator: … with a warning above it. Shells it can't use are greyed, with the reason.

Nothing of yours can borrow its rights

  • Programs DNN Manager runs as Administrator don't take .NET, NuGet, Docker or sqlcmd settings from your environment. Windows PowerShell only finds the modules of Windows and Program Files, and docker reads a configuration of DNN Manager's own instead of your .docker.
  • Saved settings and DNNMANAGER_* environment variables are held to the same rules. An IIS feature's name must be a Windows feature name, and Docker's container and volume names plain names.
  • DNN Manager only signs in with your Windows account to a SQL Server on this PC or the one in Settings → Database server. For any other server a site's web.config names, Open in SSMS, portal-alias edits, Upgrade and Restore ask first.
  • A site can no longer change another site: IIS's shared groups only read a site's folder. Sites made by an earlier version, which gave them Full control, are corrected at the start.
  • Unpacking a backup or a DNN package never writes through a link, a hard link or an alternate data stream, keeps its hands off web.config and the database however their names are written, and refuses a package that wouldn't leave 512 MB free.
  • Remove… and alias edits ask before touching a database that isn't the project's own, and Close and delete defaults to No.

The SQL container and Docker, working again

  • Docker Desktop installed for your account only works: its docker runs as you, without administrator rights, instead of being taken for Not installed.
  • New sites connect to the SQL container at 127.0.0.1,1433, which DNN's own SQL client reaches - localhost,1433 made DNN's installation fail with Could not connect to database.
  • Set up docker-compose publishes the container on [::1] too and points sites whose web.config says localhost,1433 at 127.0.0.1,1433.
  • Set up docker-compose is off until the Docker card finds Docker's engine running, and says what is missing; the card tests by itself when it is first shown.
  • A data volume made by DNN Manager 1.7.1 or older still has that version's default sa password: Set up docker-compose finds it, puts it in Settings → Database server and makes the container again with it.
  • When DNN can't connect to its database, the Output tab says why: what SQL Server answers the site's own connection string, and the error DNN logged.

Cancel and undo you can rely on

  • Cancelling a backup or restore in the SQL container ends it there too, before the undo drops anything.
  • Each undo step has a time limit. Press Cancel again - it now says Stop undoing - to stop an undo that hangs; what wasn't undone is named on the Output tab. Quitting offers Quit now when an undo takes long.
  • An operation that didn't finish because DNN Manager or Windows ended is named at the next start, with what it may have left half done.
  • Host project restores a backup beside the existing database and swaps it in once it is complete. Restore backup checks the whole backup before it writes anything.
  • Programs DNN Manager started end with it, and signing out or shutting down while an operation runs waits for it to be undone (up to a minute).

Clearer to read, easier with the keyboard

  • A long message shows its first sentence; Details (or Show output) has all of it, and so does the log file. Explanations in Settings and Troubleshoot are shorter.
  • Menus - the gear's, right-click menus, the tray icon's - and drop-down lists look like the messages: a quiet border and a soft shadow. Text in Settings, the tour, messages and menus is sharper.
  • Icon buttons - IIS Start, Stop and Restart, removing a host name or a feature, the password's eye - are reachable with Tab, and the focus ring shows on every button. The command palette has the IIS commands too.
  • A field's error is read out and becomes the field's help text; a project row tells a screen reader its DNN version, database and SQL state.
  • Links, muted text, the current search match and the SUCCESS label have enough contrast in both themes.
  • Messages wait their turn instead of replacing each other, and start-up warnings show as a message too, with Show output.

Your data under control

  • Settings → Projects → Backups → Keep backups and deployment packages: choose to delete them after a week, a month or a year. They are kept for good by default, and a clone says where it keeps its copy of the source database.
  • Troubleshoot → Clean up data → Old settings files deletes the files older versions kept their settings in, which may hold the sa password in plain text.
  • DNN Manager warns when your Documents folder is copied to OneDrive or a network share, and a password put on the clipboard is taken off when DNN Manager quits.
  • A failed update keeps its logs in Documents\DnnManager\logs\update-failed-<version>.log, and Show log opens that file.

Other changes

  • A saved setting that breaks a rule goes back to its default at the start, with a warning naming it, instead of keeping DNN Manager from starting.
  • Long stages on the Output tab show their first 200 and last 300 lines; every line is still in the log file. The log is written in batches, and all logs together stay under 200 MB.
  • Closing the window shows no Windows notification any more - the icon by the clock stays.
  • Settings → Keyboard shortcuts opens faster.
  • When a terminal without administrator rights can't be made, none is opened in its place.
  • The SQL container's image is pinned to SQL Server 2022 CU27 instead of 2022-latest, and SqlPackage to version 170.5.96.
  • Kept DNN packages are checked against GitHub's SHA-256 offline too.
  • Each release is published only after a person approves it, once a test install has started DNN Manager.
  • Fixed: DNN Manager refused every program in Program Files and Windows - dotnet, so the backup before an upgrade, Back up and Export for deployment; PowerShell; schtasks - as one "programs without administrator rights could change".
  • Fixed: a new project named like one renamed since took over the renamed site's SQL login; Remove… left a renamed site's login behind, and couldn't drop one still in use.
  • Fixed: Export for deployment of a site whose file is Web.config left the local one, with this PC's connection string, in the package.
  • Fixed: Reset to defaults couldn't get past an sa password encrypted by another Windows account or on another PC.
  • Fixed: a temporary DNN package was left behind when New project failed or was cancelled.
  • Fixed: after Uninstall from Setup's first page, Setup didn't come back as a new install.

Upgrading

Install over 1.8.1 as usual. Your settings keep their format; DNN Manager's database is upgraded at the first start.

  • Setup now asks for administrator rights. A per-user installation keeps updating where it is - let Setup move it to Program Files, then turn Start DNN Manager when you sign in on again.
  • Terminals now run without administrator rights. Use New Administrator terminal for commands that need them.
  • Run Settings → Docker container → Set up docker-compose once, also when the container already runs: it is made again with the pinned image and published on [::1] too, and sites that say localhost,1433 are pointed at 127.0.0.1,1433. Your databases stay, because they live in the data volume.
  • At the first start, sites made by an earlier version lose the Full control IIS's shared groups had on their folders.
  • A site with Windows authentication on another SQL Server shows no live SQL state unless that server is the one in Settings → Database server.
  • Junctions made without administrator rights - a module folder linked into DesktopModules, say - aren't followed. Make them again from an administrator prompt.

Tested

  • New project with DNN 10.4.0 on IIS Express, three ways: on a SQL Server container, with a SQL login of its own on an empty database, and with Manual DNN setup. Each site shows its home page - not the installation wizard - and DNN logged no error.
  • A site's connection to the SQL container, with t...
Read more

v1.8.1

Choose a tag to compare

@Albadit Albadit released this 09 Oct 10:09

DNN Manager 1.8.1

Your projects stay out of each other's way. Import, Clone, Host project and New project no longer touch another project's database or IIS site, and a failed operation takes back what it made. DNN Manager is also safer with its Administrator rights and works with screen readers.

Highlights

Each project keeps its own database and site

  • Importing a zip that you exported on this PC under a new name no longer restores into the original project's database or moves its portal alias. The new project always gets a database of its own, and its web.config points to it.
  • A name used by an IIS site that serves another folder is refused while you type, in New project, Clone, Import and Host project. Before, that site was replaced.
  • Host project doesn't take over a database that another IIS site uses. It makes one under the project's own name.
  • Clone checks everything before it copies a file. It reads the source's database from the source's own web.config, and stops if the local SQL Server can't be reached, rather than leaving a copy that uses the source's database. It asks before replacing a database of the clone's name (Replace database or Keep it), and the copy replaces the old one only once it is complete.
  • Remove… keeps a database that another IIS site uses too, and says when a database couldn't be dropped.

A failed operation leaves nothing half made

  • When New project, Clone, Import or Host project fails (an offline download, an IIS error), the folder, site and database it made are taken away again, as after Cancel. You can use the same name straight away. Only a failed DNN installation is kept, so you can look into it.
  • Quitting DNN Manager while an operation runs waits for it to stop and put back what it did.
  • A DNN upgrade step that fails unexpectedly is rolled back. Before, it left the site half upgraded.
  • Restore backup imports the database before it touches the site's files, so a failed import leaves the project as it was.

Safer with Administrator rights

  • Updates are downloaded into %ProgramData%\DnnManager\temp, which only administrators can change, and checked again just before they are installed. A release that GitHub lists no SHA-256 for isn't installed.
  • DNN Manager starts docker, dotnet, winget, PowerShell 7 and Git Bash only from a copy installed for all users, which no other program you run can swap.
  • Editors such as VS Code and Rider open as you, not as Administrator.
  • A new site signs in to the SQL container with a login of its own instead of sa. A new installation makes up its own sa password and has no default DNN host password.
  • The projects folder is limited to SYSTEM, Administrators and you.
  • A password copied for SQL Server Management Studio stays out of Windows' clipboard history and cloud clipboard, and is cleared after 60 seconds.

Screen readers and the keyboard

  • Every field and icon button has a name that screen readers read out. The Logs tab and the terminal are read as documents, and toasts are announced.
  • Error, success and warning text in the light theme, field borders and the dark theme's focus ring now have enough contrast. Windows' Contrast themes are followed.
  • Ctrl+A ticks every row on the Projects page. The command palette (Ctrl+Shift+P) can choose the columns, sort the projects, and make the sidebar and the bottom panel bigger or smaller.
  • Create project says what is still needed before it can start, for example Still needed: a DNN version, a database.

Lighter while it runs

  • The Output tab updates once a second while an operation runs, instead of ten times.
  • Project files are copied four at a time, and zips are made with fast compression.
  • The bottom panel's search stops after a set time instead of freezing the window on a difficult pattern.
  • A LocalDB database is no longer checked every 10 seconds, which kept LocalDB running.

Other changes

  • Settings → General → Look for a newer DNN Manager when it starts: switch it off and only Settings → About asks GitHub.
  • Remove… offers to delete the project's backups too (Delete backups or Keep backups).
  • Troubleshoot → Clean up data → Deployment packages deletes the packages made by Export for deployment.
  • The Output tab no longer lists the sites kept warm under Background: the Projects page already shows them.
  • A copy of the hosts file is kept as hosts.dnnmanager.bak, next to it, before each change. International host names are written in punycode.
  • A download that receives nothing for a minute fails instead of waiting forever.
  • A day's log file stops at 50 MB, and old log files are deleted when the day changes.
  • Each release on GitHub lists every file's SHA-256 in SHA256SUMS.txt.
  • Fixed: Clone failed from a SQL Server with Windows authentication and from SQL Server Express.
  • Fixed: portal aliases lost the site's port, and a DNN site with an objectQualifier didn't get its aliases and SSL fixed after a clone, import or Host project.
  • Fixed: a failed drop or restore left the database in single-user mode. Renaming and dropping work on Azure SQL Database.
  • Fixed: editing bindings lost each binding's IP address, stopping a site stopped an app pool that another site's application used, and renaming a site only in capitals failed.
  • Fixed: the DNN version list missed the oldest releases.
  • Fixed: Export for deployment didn't find a Web.config with other capitals, and a zip export failed on a file older than 1980.
  • Fixed: sites sharing an app pool showed no CPU.

Upgrading

Install over 1.8.0 as usual. Your settings keep their format.

  • An existing installation keeps its sa and DNN host passwords. If yours is still Admin@123, change it in Settings → Database server and Settings → Projects.
  • At its first start DNN Manager limits the projects folder (C:\DNN) to SYSTEM, Administrators and you. Every other account on the PC loses access to it. With many sites this can take a moment.
  • docker, dotnet, winget, PowerShell 7 and Git Bash must be installed for all users. SqlPackage is installed again into %ProgramData%\DnnManager\tools the first time it is needed, and a copy in ~\.dotnet\tools isn't used.
  • Sites made before keep signing in as sa. New ones get a login of their own.

Tested

  • All 290 fast automated tests pass, up from 220. New ones cover Import, Host project and Clone keeping to their own database, refusing the name of an IIS site that serves another folder, binding addresses, the projects folder's permissions, the update's checks, the hosts file's copy and punycode, search stopping on time, every page and the main window loading, and names for screen readers.

Full list of changes: CHANGELOG.md

SHA-256

fd102096e677d6a78230bfad2790fa7ce5f900f01551907febe4d971344bc8ef  DnnManager_Portable-1.8.1-x64.exe
1d5bdddf12f4b33092c1d3f5a08577a138dc49334da652c6e8571a6a1d29abc6  DnnManager_Setup-1.8.1-x64.exe