You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is one key potential breaking change to be aware of: if you are targeting PostgreSql database, please note that changes to the Npgsql Entity Framework Core Provider at version 6.0 now mean that the recommended way of handling Timestamp values is to migrate any "timestamp without time zone" columns to "timestamp with time zone", and always use either DateTime with Kind=Utc or DateTimeOffset with offset 0. See details here: https://www.npgsql.org/efcore/release-notes/6.0.html?tabs=annotations
This release of cloudscribe implements the above migration on some key columns in the database (e.g. the cs_user table, and SimpleContent cs_page and cs_post) but you should be aware of the potential for timezone offset bugs in any similar columns of your own. We would recommend that you take a backup of your existing application database before applying this major version upgrade.
New Visual Studio template for .NET 6.0 with Bootstrap 5 views published here https://marketplace.visualstudio.com/items?itemName=joeaudette.cloudscribeProjectTemplate
For guidance on using the template please see https://www.cloudscribe.com/introduction
This template is for Visual Studio 2022.
See https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-6 for information about what's new in .NET 6.
There is one key potential breaking change to be aware of: if you are targeting PostgreSql database, please note that changes to the Npgsql Entity Framework Core Provider at version 6.0 now mean that the recommended way of handling Timestamp values is to migrate any "timestamp without time zone" columns to "timestamp with time zone", and always use either DateTime with Kind=Utc or DateTimeOffset with offset 0. See details here: https://www.npgsql.org/efcore/release-notes/6.0.html?tabs=annotations
This release of cloudscribe implements the above migration on some key columns in the database (e.g. the cs_user table, and SimpleContent cs_page and cs_post) but you should be aware of the potential for timezone offset bugs in any similar columns of your own. We would recommend that you take a backup of your existing application database before applying this major version upgrade.
If you would like to use the .NET Core 3.1 template, or the .NET 5.0 templates, these can be downloaded here https://github.com/cloudscribe/cloudscribe.templates/blob/master/Archive/
The text was updated successfully, but these errors were encountered: