By Trent L. Taylor - 8/26/2026
StrataFrame V1 for .NET 10 — Release 1.8.2026.1The V1 framework you already use — Base, Business, UI, Security, DBEngine, Enterprise — retargeted from .NET Framework 4.8 to net10.0-windows and delivered as NuGet packages.| Release | 1.8.2026.1 | Target | net10.0-windows | Date | 26 Aug 2026 | Packages | 9 |
What this isThis is the same StrataFrame V1 codebase, with the same assembly names, namespaces, class names, and strong-name key. Your existing code should compile against it with few or no changes beyond what .NET 10 itself requires. It is not StrataFrame V2 (the WPF/MVVM framework), and it does not change the V1 programming model.The packages are provided as-is for developers who want to move existing V1 applications forward. Read the What changed section below before you start — most of what you'll hit is a .NET runtime difference, not a StrataFrame one.
PackagesNine packages, one per assembly. Package IDs carry a V1 segment so they never collide with StrataFrame V2 packages on the same feed. Each package declares its own dependencies, so referencing a top-level package pulls in everything beneath it — StrataFrame assemblies and third-party libraries alike.| Package | Assembly | Also brings in |
|---|
| ▸ StrataFrame.V1.UI | MicroFour StrataFrame UI.dll | Base, Business, Lzma | | ▸ StrataFrame.V1.UI.Expanded | MicroFour StrataFrame UI Expanded.dll | UI, Base, Business, Lzma · System.Data.OleDb | | ▸ StrataFrame.V1.Security | MicroFour StrataFrame Security.dll | UI, Base, Business, Lzma · SQL Server SMO, DirectoryServices | | ▸ StrataFrame.V1.DBEngine | MicroFour StrataFrame DBEngine.dll | UI, Base, Business, Lzma · SQL Server SMO | | ▸ StrataFrame.V1.Enterprise.Client | MicroFour StrataFrame Enterprise Client.dll | Enterprise, Base, Lzma | | StrataFrame.V1.Enterprise | MicroFour StrataFrame Enterprise.dll | Base, Lzma | | StrataFrame.V1.Business | MicroFour StrataFrame Business.dll | Base, Lzma | | StrataFrame.V1.Base | MicroFour StrataFrame Base.dll | Lzma · Microsoft.Data.SqlClient, Oracle ODP.NET Core, System.Data.OleDb | | StrataFrame.V1.Lzma | MicroFour StrataFrame Lzma.dll | — |
▸ marks the top-level packages. Most applications reference StrataFrame.V1.UI and add Security, DBEngine, UI.Expanded, or Enterprise.Client as needed. You should not need to reference Base, Business, Lzma, or Enterprise directly.
InstallThese packages are not on nuget.org. All nine are bundled in a single download attached to this thread: SF1_Nuget_1.8.2026.1.zip. NuGet cannot read packages from inside a zip, so you extract it to a folder and point NuGet at that folder — the folder becomes a private package source that works exactly like nuget.org from Visual Studio's point of view.1. Extract the zipUnzip SF1_Nuget_1.8.2026.1.zip to a folder you'll keep, for example C:\NuGet\StrataFrameV1\. After extracting, that folder should contain the nine .nupkg files directly — not a subfolder. If Windows created a nested folder inside, use that inner folder as the source in the next step.C:\NuGet\StrataFrameV1\ StrataFrame.V1.Base.1.8.2026.1.nupkg StrataFrame.V1.Business.1.8.2026.1.nupkg StrataFrame.V1.DBEngine.1.8.2026.1.nupkg StrataFrame.V1.Enterprise.1.8.2026.1.nupkg StrataFrame.V1.Enterprise.Client.1.8.2026.1.nupkg StrataFrame.V1.Lzma.1.8.2026.1.nupkg StrataFrame.V1.Security.1.8.2026.1.nupkg StrataFrame.V1.UI.1.8.2026.1.nupkg StrataFrame.V1.UI.Expanded.1.8.2026.1.nupkg Don't delete the folder after installing. NuGet copies packages into its cache on first restore, but a clean checkout or a cache clear will need the source folder again. Future releases will ship as a new zip; extract them into the same folder and NuGet will offer the newer version as an update.2. Register the folder as a package sourceVisual Studio: Tools → Options → NuGet Package Manager → Package Sources → click the + button. Name it "StrataFrame V1" (or anything), set Source to the folder from step 1, click Update, then OK.Command line:dotnet nuget add source "C:\NuGet\StrataFrameV1" --name StrataFrameV1 Either method registers the source for your user account (it's written to %AppData%\NuGet\NuGet.Config), so it applies to every solution you open.3. Install into your projectVisual Studio: right-click the project → Manage NuGet Packages → change the Package source dropdown (top right) to the source you just added → Browse → install StrataFrame.V1.UI plus any other top-level packages you use (Security, DBEngine, UI.Expanded, Enterprise.Client). The dependent packages install automatically.Command line:dotnet add package StrataFrame.V1.UIdotnet add package StrataFrame.V1.Security 4. Remove the old referencesDelete your existing file references to the StrataFrame DLLs in Common Files\MicroFour\StrataFrame. The package references replace them, and leaving both will produce ambiguous-type errors.| Requirement: your application project must target net10.0-windows and be SDK-style with <UseWindowsForms>true</UseWindowsForms>. A .NET Framework 4.x project cannot consume these packages. If you are still on the old project format, run the Upgrade Assistant or convert the project file first. |
Not included in this releaseEnterprise ServerThe server is an ASP.NET WebForms web application and has no direct path to .NET 10 — it needs to be rebuilt on ASP.NET Core. StrataFrame.V1.Enterprise.Client is included so client-side code compiles; using it against an existing .NET Framework Enterprise Server has not been tested and is not supported in this release.WebForms controlsThe WebForms Controls and WebForms Extended Controls in the UI assembly depend on System.Web, which does not exist in .NET 10. They are excluded. WebBasics and WebRowPopulatingEventArgs are excluded for the same reason.Legacy connection-string wizard pagesDBEConnectionStringShared, DBEAddNewConnectionString, and DatabaseConnectionWizard are excluded from the UI assembly. The current ConnectionWizard, SharedSettingsWizard, and the SQL Server / Oracle / OLEDB connection pages are all present.Everything elseVisual Studio integration (the Business Object Mapper, Add-Ins), Inherited UI, Infragistics Wrapper, Extensibility, Security Maintenance, and the WinForms designer tooling are not part of this drop.
What changedMost of these are consequences of the .NET runtime, not StrataFrame decisions. You will hit them in your own code as well.SQL Server: System.Data.SqlClient → Microsoft.Data.SqlClientAny code that references SqlConnection, SqlCommand, SqlParameter, etc. directly must change its Imports / using to Microsoft.Data.SqlClient. The package arrives automatically with Base.SQL Server: encryption is on by defaultMicrosoft.Data.SqlClient 4.0+ defaults to Encrypt=True. If your server uses a self-signed certificate, connections that worked under .NET Framework will fail with a certificate-trust error. Either install a trusted certificate on the server or add TrustServerCertificate=True to your connection string.Oracle: System.Data.OracleClient → Oracle ODP.NET CoreThe Oracle data source now uses Oracle.ManagedDataAccess.Core. Connection strings are largely compatible; consult Oracle's documentation for provider-specific keywords.OLEDB and Excel import/exportSystem.Data.OleDb is now a NuGet package (included automatically). Note that the Jet 4.0 provider used by ExcelHelper is 32-bit only — build your application for x86 if you rely on it, or pass an ACE provider name.No GAC, no Common Files folder.NET 10 has no Global Assembly Cache. StrataFrame assemblies now live in your application's output folder alongside their dependencies. There is nothing to install on end-user machines beyond the .NET 10 Desktop Runtime.WinForms designer analyzer WFO1000.NET 9+ treats WinForms analyzer WFO1000 as an error by default. Custom controls that inherit from StrataFrame controls will likely trigger it on public properties. Add the following to your project file, or annotate properties with DesignerSerializationVisibility:$(NoWarn);WFO1000 Extra language folders in your outputYou will see folders such as de, ja, zh-Hans in your build output. These are localized resources from Microsoft.Data.SqlClient and its dependencies, not from StrataFrame. To suppress them add this to your project file:en Strong namingAssemblies are signed with the same StrataFrame key as before, so any InternalsVisibleTo or public-key-token checks continue to match.| Testing status. These packages compile cleanly and have been verified to restore and build in a fresh .NET 10 WinForms project with all dependencies deployed. They have not been run through the full V1 regression suite. Treat this as a developer preview, test your own applications thoroughly, and report what you find in this thread. |
FeedbackPost build errors, runtime exceptions, and anything that behaves differently from 4.8 as replies here. Include the package version, the stack trace, and whether you were on x86 or x64. Fixes will ship as new package versions to this same thread.
|
|