Set up your laptop for DNN development

A DNN development environment gives you a private place to build modules, connect a database and test changes to a business portal before they reach staging or production. The goal is a repeatable setup that runs on one laptop and can be rebuilt when a project changes.

DNN, or DotNetNuke, is an ASP.NET content management platform with a Microsoft SQL Server backend. You will need Windows, compatible .NET tooling, the DNN Platform files and a local database, plus Git for dependable source control.

Plan a reliable DNN laptop setup

Most Australian teams in Sydney, Melbourne, Brisbane and Perth already use Windows laptops with Microsoft 365 and Teams, although installed versions differ. Use a 64-bit machine with administrator access, enough free disk space and a separate development account rather than your everyday desktop.

Choose a short, uncomplicated project path such as C:\DNN\Work, avoid folders that require elevated permissions, and keep the project outside OneDrive’s active sync location. Synchronised folders can lock assemblies during a build.

• Check the DNN release notes for the required .NET runtime, database engine and Visual Studio version.
• Install SQL Server Express and record the instance name, authentication method and database name.
• Keep NuGet, npm and DNN extension packages versioned so another developer can reproduce the build.
• Back up source files and export the local database before major extensions or schema changes.

Install the runtime and development tools

Install the .NET runtime and SDK requested by your DNN release first. Then install Visual Studio with the ASP.NET and web development workload, SQL Server Management Studio and Git for Windows. Add VS Code or another editor only if it supports your workflow rather than duplicating unnecessary tools.

After checking the release documentation, download the DNN Platform installer from the official project source and extract it into the prepared folder. Keep the original package available so you can repeat the installation. If your team is outside major metropolitan centres, check your NBN connection before a large download: fibre-to-the-node and fixed-wireless services behave differently from fibre-to-the-premises, so cache dependencies and allow for intermittent connectivity.

Configure SQL Server and the DNN project

During SQL Server setup, use an instance such as SQLEXPRESS and decide whether to use Windows or SQL authentication. If you choose SQL authentication, enable mixed mode where appropriate, create a dedicated development login and store its password outside source control.

Complete DNN’s installation wizard, point it at that instance and create a fresh database with a project-specific name. Configure the website to use IIS Express or a local IIS site, then open the site and create the host administrator account. Save connection details in the DNN connection configuration rather than duplicating them across scripts.

Connect source control and project assets

Initialise a Git repository in your custom-code folder, not in the entire downloaded DNN Platform installation. Keep core platform files and local content separate; track your modules, templates and deployment scripts so platform upgrades do not obscure your changes.

Add a .gitignore for Visual Studio build output, packages, logs, local connection data and synchronised secrets. Branch by feature, commit tested changes and use a development branch for database scripts. Review staged files before committing, especially installation files that may contain credentials or internal URLs.

Validate the project in a local browser

Create a simple page, add a DNN module and run the application from Visual Studio. Exercise the paths your project actually uses: sign-in, editing, search, scheduled tasks and installation of any custom extension. A clean build and a successful browser request are more useful than checking only that the home page opens.

Use synthetic records rather than client or employee data. Under the Privacy Act 1988 and the Australian Privacy Principles, Australian organisations must handle personal information carefully; a development copy of a production database can still expose regulated information. Confirm your organisation’s privacy and security obligations before importing any real records.

Troubleshoot common laptop and database issues

If the site cannot reach SQL Server, confirm the instance name, login and TCP/IP settings in SQL Server Configuration Manager. Restart the service after changing network settings, and check whether a local firewall or another SQL instance is intercepting the connection.

If a build fails, check the .NET version against DNN’s requirements, clear stale Visual Studio outputs and restore packages from the lock file. For confusing timestamps, store timestamps in UTC and display them in local time: Brisbane remains on AEST, while Sydney and Melbourne move between AEST and AEDT.

Keep the environment ready for ongoing work

Keep a short setup record with DNN, .NET, Visual Studio and SQL Server versions, then rebuild the environment on a clean virtual machine or spare laptop before an important deadline. This catches missing runtimes and undocumented manual steps while there is still time to fix them.

For Australian buyers, clarify ownership of the code, support responsibilities and training costs before work starts. Agreeing an overlap between Australian and French working hours makes remote delivery smoother when a release depends on both business and technical stakeholders.

Aricie’s France-based teams in Mureils near Paris, Lyon and Grenoble provide DNN solutions, custom software and professional training. Contact Aricie to arrange remote onboarding or discuss a DNN build for your Australian organisation.