Updating from SS V8.10 to 10

ServiceStack
1

Hi,

Looking to upgrade from V8.10 to V10, is it a case of updating nugget packages? and if I am using Kamal that has modifications, do I need to update anything there?

Thanks

2

In most cases it’s just a matter of upgrading all ServiceStack package versions from 8.* to 10.* but you should go through the ServiceStack v10 Release Notes to see what’s affected.

E.g. one disruptive change is that there are now 2 different versions of Open API and Swagger UI. Basically if you had an existing one I would remove your existing packages and configuration and configure it with one of the options.

You may also want to convert your solution to use the new slnx format with dotnet sln migrate.

Quite a few changes were made to Kamal + Build Scripts, up to you if you want to apply your changes over the latest version that’s in the templates or if you just want to upgrade to use .NET 10 in your build scripts + docker files.

1 Like
3

image
image1424×216 35.4 KB

With the latest template, Postgresql versioning for the official and ServiceStack tools are not pointing to the latest versions and also there is an issue the PostgreSqlDateOnlyConverter when I upgraded all the packages manually.

Should we not upgrade the packages and leave them as is when using the provided templates?

Thanks

4

All ServiceStack packages should use the same version, to use the latest packages you should use a wild card, e.g:

<PackageReference Include="ServiceStack.OrmLite.PostgreSQL" Version="10.*" />
5

Ok was just hoping it was part the templates that is generated

6

All templates already use wildcard versions for all ServiceStack package references:

It’s only when you add an additional package (e.g. dotnet package add) does it include a hard package version, that’s the behavior of the dotnet tools that can’t be controlled.