/
5.82.99 - .NET upgrade Alpha

5.82.99 - .NET upgrade Alpha

Release Notes

eWater is pleased to announce that all projects and libraries within Source have been successfully migrated from .NET Framework 4.8 to .NET 8.0. This upgrade marks a key milestone in enhancing performance, security, and maintainability.

Before testing, please review the prerequisite documentation to ensure a smooth experience with this version:

We kindly request all users to thoroughly test this Alpha version and share your feedback and any issues you encounter. Your input is invaluable in helping us refine the product as we prepare for the Beta release, scheduled for August.

We expect the clients to send below user guide post testing, as a feedback form.

Client Testing Guide – Areas to Review for .NET 8 Upgrade

Project Title: Library Upgrade to .NET 8                                              Prepared By: [ Name]

Build Version: Alpha Build [xxxxx]                                                         Date: [DD/MM/YYYY]

Distribution: Available via Toolkit

Purpose

This document is intended to guide your team through testing the Alpha build of our application upgraded to .NET 8. It outlines the key areas for your review. While your input is valuable, please note that this is not a formal acceptance checklist. Your feedback will help us improve and plan for future releases.

 

Testing Checklist

Area

What to Look For

Comments

Prerequisites

 

 

Installation & Security

Any installation issues, security warnings, or difficulties due to corporate policies.

 

UI Performance

Slowness or lag in opening screens, entering text, or using buttons.

 

File Operations

Delays in loading/saving/creating projects (excluding first-time Firebird upgrade ~1 min).

 

Stability

Any crashes or freezes not seen in the .NET Framework 4.8 version.

 

Visual/UI Issues

Anything that looks strange, broken, or inconsistent in the interface.

 

Output Accuracy

Any change in results/output compared to the existing version (regression-tested items).

 

Workflow Disruptions

Anything that breaks or complicates your typical workflow.

 

Testing Notes & Feedback

Please use the section below to capture any issues, observations, or anomalies:

  • Issue Description:

  • Steps to Reproduce:

  • Screenshots/Logs (if available):

  • Expected vs Actual Behaviour:

  • Priority (Low/Medium/High):