Skip to main content

Installation

This guide walks you through opening the Damsy ERP solution in Visual Studio and preparing it for a first local run. Database setup and connection string configuration are covered in subsequent pages.

Purpose​

Get the solution building and the web project designated as the entry point for debugging — without yet worrying about full production data.

Prerequisites​

Complete Requirements first — you need Visual Studio, .NET Framework 4.5.2, and SQL Server available on your machine.

Step 1 — Clone or extract the repository​

Place the codebase in a path without special characters if possible. Example:

C:\Projects\damsy_erp_core\

The solution file lives at the repository root:

damsy_erp_core/
├── DamsyERP.sln
├── DamsyERP.UI/
├── DAL/
├── BO/
├── UTILITIES/
├── database-backup/
└── docs/

Step 2 — Open the solution​

  1. Launch Visual Studio.
  2. Choose Open a project or solution.
  3. Select DamsyERP.sln.

Visual Studio loads four projects: DamsyERP.UI, DAL, BO, and UTILITIES.

Step 3 — Set the startup project​

The web application must be the startup project so F5 launches IIS Express against the UI site.

  1. In Solution Explorer, right-click DamsyERP.UI.
  2. Select Set as Startup Project.

The project name appears in bold.

tip

If multiple developers share machine profiles, verify startup project after every solution reload — Visual Studio occasionally resets it to the first project alphabetically.

Step 4 — Restore NuGet packages​

Visual Studio typically restores packages automatically on open. If build errors reference missing assemblies:

  1. Right-click the solution → Restore NuGet Packages.
  2. Rebuild: Build → Rebuild Solution.

Step 5 — Verify build​

Press Ctrl+Shift+B (Build Solution). All four projects should compile without errors.

Common first-build issues:

ErrorResolution
Missing Crystal assembliesInstall Crystal Reports runtime / CR for VS
NuGet restore failedCheck network; clear NuGet cache
Framework reference errorsInstall .NET Framework 4.5.2 Developer Pack

Step 6 — Review project structure​

Confirm you can locate key entry points:

PathRole
DamsyERP.UI/Global.asax.csApplication start, HTTPS redirect, error handling
DamsyERP.UI/App_Start/RouteConfig.csDefault route → Login/Index
DamsyERP.UI/Web.configConnection strings and appSettings
DAL/BaseHelper.csConnection resolution and SP execution

See Solution structure for the full map.

Architecture after install​

At this stage IIS Express can start, but the app is not usable until Web.config points at a database with schema and seed data.

Developer notes​

IIS Express profile​

Project properties → Web tab shows the IIS Express URL and port. The default MVC route opens Login/Index — you do not need to append a path manually.

Multiple configuration transforms​

Web.Release.config transforms settings for publish (e.g., ForceHttps=false override). Local development uses base Web.config.

Do not commit secrets​

Sample connection strings in the repository may contain instance names from a developer machine. Replace with your values locally; use server-side secrets for production.

Important notes​

warning

Installation alone does not create ERP tables or stored procedures. Plan time for Connection strings and database schema setup before expecting a successful login.

Common mistakes​

MistakeResult
Starting DAL or BO as startupNothing useful runs — these are class libraries
Skipping NuGet restoreMissing reference build errors
Building without Crystal runtimeMay compile if references exist; reports fail at runtime

Next steps​

Configure your database connection in Connection strings, then follow Running locally to start the app and sign in.