Releases: DataJuggler/DataTier.Net
DataTier.NET Version 5.1.8
5.1.8 - 1.28.2025: I changed the Confirm Update Control to allow an update to continue if the method already existed in the Gateway.
I also show the database name on the New Stored Procedure Editor Control
5.1.7 - 1.27.2025: I added a new field to ProjectReferencesView. I realized the field RefernecesId was missing from the view.
If you have an existing database you will need to add this field or create a new database. If anyone needs a script let me know.
5.1.6 - 1.26.2025: A few cosmetic things to the UI and some work is in progress for the Project Converter. The Project Converter / Project Fixer is a work in progress, but helps convert existing 4 project data tiers to the new 2 project data tier.
5.1.5 - 1.25.2025: I added some features to help fix corrupt projects and a new Project Converter located in the Tools folder.
This Project Converter is also a Project Fixer and soon will be a Project Upgrader.
5.1.4 - 1.23.2025: I removed DataOperationsManager. This class is no longer needed or used.
5.1.3 - 1.23.2025: I added a validation check when you and Build if the Project Folder does not exist a message is shown.
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.NET 5.1.7
5.1.7 - 1.28.2025: I added a new field to ProjectReferencesView. I realized the field RefernecesId was missing from the view.
If you have an existing database you will need to add this field or create a new database. If anyone needs a script let me know.
5.1.6 - 1.27.2025: A few cosmetic things to the UI and some work is in progress for the Project Converter. The Project Converter / Project Fixer is a work in progress, but helps convert existing 4 project data tiers to the new 2 project data tier.
5.1.5 - 1.26.2025: I added some features to help fix corrupt projects and a new Project Converter located in the Tools folder.
This Project Converter is also a Project Fixer and soon will be a Project Upgrader.
5.1.4 - 1.23.2025: I removed DataOperationsManager. This class is no longer needed or used.
5.1.3 - 1.23.2025: I added a validation check when you and Build if the Project Folder does not exist a message is shown.
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.NET 5.1.6
5.1.6 - 1.27.2025: A few cosmetic things to the UI and some work is in progress for the Project Converter. The Project Converter / Project Fixer is a work in progress, but helps convert existing 4 project data tiers to the new 2 project data tier.
5.1.5 - 1.26.2025: I added some features to help fix corrupt projects and a new Project Converter located in the Tools folder.
This Project Converter is also a Project Fixer and soon will be a Project Upgrader.
5.1.4 - 1.23.2025: I removed DataOperationsManager. This class is no longer needed or used.
5.1.3 - 1.23.2025: I added a validation check when you and Build if the Project Folder does not exist a message is shown.
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.Net 5.1.5
5.1.5 - 1.26.2025: I added some features to help fix corrupt projects and a new Project Converter located in the Tools folder.
This Project Converter is also a Project Fixer and soon will be a Project Upgrader.
5.1.4 - 1.23.2025: I removed DataOperationsManager. This class is no longer needed or used.
5.1.3 - 1.23.2025: I added a validation check when you and Build if the Project Folder does not exist a message is shown.
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
v5.1.4
5.1.4 - 1.23.2025: I removed DataOperationsManager. This class is no longer needed or used.
5.1.3 - 1.23.2025: I added a validation check when you and Build if the Project Folder does not exist a message is shown.
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.Net 5.1.3
5.1.3 - 1.23.2025: I added a validation check when you and Build if the Project Folder does not exist a message is shown.
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.NET 5.1.1
5.1.1 - 1.15.2025 - I realized when I converted to static methods I broke the app because the connection name was stored in the App Controller. To fix this I know pass in a Data Manager to each data method and it seems to work in my initial testing.
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.NET 5.1.0
5.1.0 - 1.13.2025: I have streamlined the app a little more. I took out the Controller Manager and the Data Operations Manager classes.
Now more of the classes are Static methods, so there should be less memory used to a small degree.
I have broken earlier versions, when I get some time I will try and back fit older versions. For now its easier to recreate a new data tier.
I realize if you have a lot of custom methods this could be a pain.
Possible next big update is removing the Stored Procedure Classes and refactoring the Stored Procedure Manager to use XML or JSon to store the procedure names and parameters.
-- Version 5.0.4 Notes
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.NET 5.0.4
5.0.4 - 1.11.2025: This release fixes the Remove Table Code for V2 Templates.
-- Version 5.0.3 Notes
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated
DataTier.NET 5.0.3
5.0.3: This new version now plays a mild tone when a message is displayed. I took out the Message Boxes and use a Display Message.
I am working on a setting for sound, but for now if you open DataTier.Net.config in the install folder and edit it, you can set PlaySounds = false. Or run the development version using Visual Studio 2019 and modify the app.config.
<add key="PlaySound" value="false" />
The indent should be fixed for custom methods.
Existing Projects Breaking Change
Existing projects that were created prior to 5.0.0 release are broken. I will build a tool to fix it when I get some time.
The reason for the breaking change is I realized all the methods created using the Data Manager could be static methods.
I was instantiating a class for each table in the data manager and it served no benefit. The fix is to remove this.DataManager.
this.DataManager.CustomerManager.FindCustomer(
becomes
CustomerManager.FindCustomer(
Sorry for the breaking change, but running more efficiently is always better.
-- Carried over from 5.0.2
Big Update. DataTier.NET now targets .NET 9.
New project templates have been created for .NET 9 also.
Message Boxes have been replaced by a Message Display Control, making screen messages look a little nicer and without a loud noise while recording.
Note: The Blazor Data Services Control has been removed. It was a neat feature, but I realized I had not used it in all of .NET 8, so I just removed the code for the Blazor Data Services Control and related changes to the Project Editor.
The database no longer has these fields, so you must use the new database in the Database Folder of this project.
Version 2 Templates are the only templates going forward, so all new projects will only have two projects in the Data Tier.
- Data Access Component
- Object Library
Existing Projects or new projects for .NET 8 or lower will still work. It is recommended to use .NET 9 for all new projects.
All new development will be for .NET 9 unless a major bug is found in an earlier version.
Existing Users - Breaking Database Changes
The database has changed. In the Project Table, you can drop the columns:
- Enable Blazor Features
- Services Folder
Update the Stored Procedures from the file DataTier.NET.Database.sql, located in the Databasebase\SQLScripts folder of this repo.
Last Breaking Change Is All New Projects, The Data Manager folder is now called Data, so the DataManager class is not in a namespace
named DataManager. Existing projects already have the database value saved so they should not be affected.
Carried over release notes for prior versions:
(Current Release)
DataTier.Net 4.9.5 - Fixed a major bug where the Project References had duplicates. Now there is a constraint on the ProjectReferences table to not allow duplicates by ReferenceName and ProjectId. Also, now you can double click on the Project References in the References Set Editor to open.
(legacy)
DataTier.Net 4.9.3
A vulnerability was found in System.Data.SqlClient, so I update the NuGet package to 4.8.6.
DataTier.Net 4.9.2
This release was created because DataTier.Net now has a new Version 2 template structure with only two projects:
Data Access Component
Object Library
All the functionality is the same for now as the 4 project structure. Two projects makes it simpler to deploy.
The Object Library could be included in the Data Access Component, but I think it is better to separate them.
After installation, follow these steps:
Create a SQL Server Database named DataTier.Net.Database
Run DataTier.Net and follow the instructions on the Setup screen to create your SQL Server database DataTier.Net.Database.
The Setup Control will walk you through setting up DataTier.Net and and creating your connection string and Environment Variable.
Manual Installation (legacy)
The typical location of database scripts:
C:\Program Files (x86)\DataJuggler\DataTier.Net\SQL Scripts\DataTier.Net.Database.Schema.sql
Execute the script DataTier.NET.Database.Schema.sql
Create a User Level Environment Variable named DataTierNetConnection, and set the value to a connection string for your DataTier.Net.Database.
Tip: Connection Builder is installed and will have a shortcut on your desktop. Use Connection Builder to create your connection string.
Example Connection String using Windows Authentication. Replace (Server Name) with your Server Name.
Data Source=(Server Name);Initial Catalog=DataTier.Net.Database;Integrated Security=True;Encrypt=False;
Fixes
Fixed in version 4.9.2: Confirm Changes Control and Confirm Removal Control now handle the new Data Manager folder to Data for V2 projects.
Fixed in version 4.9.1: DataTier.Net Database was updated