Ventura SQL 1.100.53 is available for download.
Version 1.100 is a major update.
What is new:
- The Ventura runtime libraries are delivered as .NET Standard 2.0 class libraries.
- ASP.NET Core 2.0 support.
- The out-of-box experience is vastly improved. When you create a new project, Ventura SQL Studio creates sample Visual Studio projects in the Ventura SQL project folder.
- References to C# projects in Ventura's .venproj file are now using relative file paths.
Ventura SQL compiled for .NET Standard 2.0 will run on the following platforms:
- .NET Framework 4.6.1;
- .NET Core 2.0;
- Mono 5.4;
- Xamarin.iOS 10.14;
- Xamarin.Mac 3.8;
- Xamarin.Android 7.5;
- UWP targetting Fall Creators Update (FCU, Build 16299) as the minimum version of your UWP project.
The upcoming version 1.100 of Ventura SQL comes with sample projects that can be used as a template for implementing Ventura in your projects.
In the "New Project" dialog, simple leave the "Create sample" checkbox checked an then sample client and server (ASP.NET and ASP.NET Core 2.0) projects will be installed in the project folder.
Version 1.100 is currently in beta testing.
The upcoming version 1.100 of Ventura SQL comes with runtime DLLs for ASP.NET Core 2.0.
An ASP.NET Core web server project can be used as the middle-tier.
There is not that much to tell about ASP.NET Core support as it functions similar to the current ASP.NET runtime.
The upcoming version 1.100 of Ventura SQL will contain runtime DLLs that are compatible with .Net Standard 2.0
.NET Standard solves the code sharing problem for .NET developers across all platforms by bringing all the APIs across the environments: desktop applications, mobile apps & games, and cloud services.
This means that the same VenturaSQL.Standard20.dll can be used in .Net Framework, .Net Core and Xamarin projects.
We will target the latest .Net Standard 2.0 specification.
.NET Standard 2.0 is supported on the following platforms:
- .NET Framework 4.6.1
- .NET Core 2.0
- Mono 5.4
- Xamarin.iOS 10.14
- Xamarin.Mac 3.8
- Xamarin.Android 7.5
- UWP targetting Fall Creators Update (FCU, Build 16299) as the minimum version of your UWP project
The spirit of Christmas should not be just for one day but for the whole year! Wishing you love, joy and peace the whole year round. Merry Christmas!
Support for .Net Standard is in the works.
.NET Standard solves the code sharing problem for .NET developers across all platforms by bringing all the APIs across the environments: desktop applications, mobile apps & games, and cloud services:
This means that the same Ventura SQL DLL can be used in .Net Framework, .Net Core and Xamarin projects.
We expect adoption for .Net Standard to be slow.
In preparation for the yet to be announced Ventura UX product, the Ventura Data Access Layer will be renamed to Ventura SQL.
We are currently in the process of updating the website and the product documentation.
Within the next 2 weeks we will release Ventura SQL 1.0.200 that will implement the new naming.
The EXE and DLL names and NuGet Id's will change.
EXE and DLL names
VenturaStudio.exe becomes VenturaSQLStudio.exe
VenturaUWP.dll becomes VenturaSQL.UWP.dll
VenturaAndroid.dll becomes VenturaSQL.Android.dll
VenturaIOS.dll becomes VenturaSQL.IOS.dll
VenturaWPF.dll becomes VenturaSQL.WPF.dll
VenturaWinForms.dll becomes VenturaSQL.WinForms.dll
VenturaAspNet.dll becomes VenturaSQL.AspNet.dll
Ventura.UWP becomes VenturaSQL.UWP
Ventura.Android becomes VenturaSQL.Android
Ventura.iOS becomes VenturaSQL.iOS
Ventura.WPF becomes VenturaSQL.WPF
Ventura.WinForms becomes VenturaSQL.WinForms
Ventura.AspNet becomes VenturaSQL.AspNet
Priority support is an optional service for business customers who need a guaranteed response time of one business day.
Customers will be given an email address to contact support directly.
The price is US$ 500,00 per developer per year.
Click here for more information.
Input and output parameters for Sql Server commands are Nullable, meaning they can always contain the value NULL. This is a feature of Sql Server.
For this reason, the generated C# Recordset code will always implement the Nullable type. Like the 'int?' in this example:
An example of a Nullable output parameter:
I am thrilled to announce that the online store is open as of today.
License Keys will be delivered instantly when an order is completed.