Skip to content

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 the SQL client DNN uses: 127.0.0.1,1433 signs in at once, localhost,1433 fails with the error DNN's installation showed.
  • All 442 fast automated tests pass, up from 290. New ones cover the settings' rules and resetting a bad value, the environment programs get, unpacking crafted packages, junctions and hard links, the launcher's environment, undo time limits, the log cap, contrast in both themes, the message queue, programs run as you, the programs Windows owns, the container's addresses and an old volume's password, and the site's database address.

Full list of changes: CHANGELOG.md

SHA-256

e5255d8a2e958e9d47300311f3d08d158ac30fd1bfec6ca1ae38cab090e01fd7  DnnManager_Portable-1.8.2-x64.exe
7f9af416a511c1447f6ff987f7cda725540f330df3f42d90068d575bf3d2b15f  DnnManager_Setup-1.8.2-x64.exe