Requirements
Before you open the Damsy ERP solution, confirm your development machine meets the prerequisites below. Damsy ERP targets Windows with .NET Framework 4.5.2 and SQL Server — it does not run on .NET Core or Linux without significant rework.
Purpose
This page lists every runtime, tool, and optional component you need for local development and for environments that host Crystal Reports viewers.
When to use this checklist
- First-time setup on a new developer machine
- CI/build agent configuration for compile-and-publish pipelines
- Staging or production server preparation (IIS deployment)
Required software
| Component | Minimum | Notes |
|---|---|---|
| Operating system | Windows 10/11 or Windows Server 2016+ | IIS Express (dev) or full IIS (prod) |
| Visual Studio | 2019 or 2022 | Workload: ASP.NET and web development |
| .NET Framework | 4.5.2 Developer Pack | Matches targetFramework in Web.config |
| SQL Server | 2016+ (Express is sufficient) | LocalDB or named instance (e.g., localhost\SQLEXPRESS) |
| SQL Server Management Studio | Latest compatible | Schema export, seed scripts, debugging SPs |
| IIS Express | Included with Visual Studio | Default F5 debug host |
The repository may reference a specific SQL instance in sample connection strings (e.g., BRAJESH\SQLEXPRESS). Update these to match your instance name during setup.
Optional but strongly recommended
| Component | Why you need it |
|---|---|
| SAP Crystal Reports runtime | Report viewer .aspx pages require CR engine 13.0.2000.0 assemblies |
| Crystal Reports for Visual Studio | Design-time editing of .rpt files |
| Git | Source control (solution is Git-tracked) |
Crystal Reports runtime notes
Crystal Reports is a common source of "works on my machine" failures:
- Version alignment — Web.config references
CrystalDecisions.*assemblies at version 13.0.2000.0. Install the matching runtime (CR for Visual Studio / SAP Crystal Reports runtime engine for .NET Framework). - Publish target — The runtime must exist on the IIS server, not only on the developer PC.
- Image handler —
CrystalImageHandler.aspxis registered in Web.config; IIS integrated mode must allow this handler.
If report pages throw Could not load file or assembly 'CrystalDecisions.*', install or repair the Crystal Reports runtime before debugging application code.
Database requirements
Damsy ERP expects a SQL Server database with:
| Object type | Approximate count |
|---|---|
| Tables | ~185 |
| Stored procedures | ~887 |
A blank database created from repository scripts provides the container only. Full schema must be exported from a working database and applied separately (see Running locally).
Running against an empty database without schema will cause immediate failures on login — stored procedures such as GetLoginUser and GetCompany must exist before the app is usable.
Hardware guidelines
| Resource | Development | Production (small team) |
|---|---|---|
| CPU | 4 cores | 4+ cores |
| RAM | 8 GB minimum, 16 GB recommended | 16 GB+ |
| Disk | SSD recommended | SSD for SQL data files |
Large Excel imports and Crystal report generation are memory-intensive. Web.config allows uploads up to 100 MB (maxRequestLength / maxAllowedContentLength).
Network and ports
| Service | Default |
|---|---|
| IIS Express | Random port assigned by Visual Studio (check project properties) |
| SQL Server | 1433 (default instance) or dynamic port for named instances |
No outbound internet is required for core ERP operation. E-invoice (IRN) features need network access to configured ZAPI endpoints when used.
Developer notes
Visual Studio workloads
Ensure these are installed:
- ASP.NET and web development
- .NET desktop development (for Crystal designer tools, if editing reports)
- Data storage and processing (SSMS integration)
SQL Server authentication
Sample Web.config uses Integrated Security (Windows auth). SQL authentication works if you update connection strings accordingly — never commit production passwords to Git.
Browser
Use a modern Chromium-based browser or Edge. Legacy IE-specific code is minimal; jQuery and DataTables expect ES5-compatible browsers.
Common mistakes
| Mistake | Symptom |
|---|---|
| Only SQL Server LocalDB without full schema | Login fails — missing SPs |
| Visual Studio without web workload | Solution opens but IIS Express unavailable |
| Crystal runtime missing on IIS server | Reports work locally, fail after publish |
| Wrong .NET Framework version | Build errors or runtime binding failures |
Related pages
Next steps
Install the prerequisites above, then follow Installation to open and configure the solution.