Umbraco-CMS: v10.0.0-rc upgrade Error: Conflicting assets with the same target path 'umbraco/assets/css/canvasdesigner.min.css'.

The main changes between v9 and v10 templates

Program.cs

Updated to

 public class Program
    {
        public static void Main(string[] args)
            => CreateHostBuilder(args)
                .Build()
                .Run();

        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureUmbracoDefaults()
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStaticWebAssets();
                    webBuilder.UseStartup<Startup>();
                });
    }

wwwroot/*

Remove:

• wwwroot/umbraco folder

umbraco/*

Remove:

• umbraco/config/lang
• umbraco/PartialViewMacros
• umbraco/UmbracoBackOffice
• umbraco/UmbracoInstall
• umbraco/UmbracoWebsite

The documentation is online https://our.umbraco.com/documentation/Fundamentals/Setup/Upgrading/version-specific#version-9-to-version-10

So I’ll close this issue.

Is umbracoDbDSN_ProviderName required or does it use Microsoft.Data.SqlClient by default if not specified?

If you omit this value, it indeed defaults to Microsoft.Data.SqlClient and therefore is only required when using SQLite right now (but it’s still best practice to explicitly set it, so you’re aware of this setting/value).

When using Umbraco Deploy using an empty connection string, it will default to using SQLite, even when you already have a LocalDB file in your data directory. As Andy mentioned you can either explicitly configure the connection string or enable the PreferLocalDbConnectionString setting. Using the setting has the benefit of being able to use the same settings for both Windows and Mac/Linux environments, as the explicitly configured LocalDB connection string won’t work cross-platform.

That’s correct yes - see some notes here in the upgrade to 10 details.

There’s also a config setting you can use to “prefer LocalDb” - documented here.

Yes, I’ve found the same here. An alternative I understand is to do a dotnet clean on your V9 install before upgrading to V10.

I think this is related to v10 changing to use embedded resources - I’ve found that deleting wwwroot/umbraco fixes the build.