Optimizely - update 387

Removed dependency to Az.Storage and Azure.Storage to make the module completely standalone.

Overwriting an existing code package is not supported (for CMS 12/Commerce 14 and above) and the deployment API throws an error when this is attempted. That error message was improved.

The notification popup in the Markets view did not have the same style as other views in  the Administration interface.

Fixed an issue where customers had to explicitly add the EcfSqlConnection connection string when configuring the application:

services.Configure<DataAccessOptions>(options =>
{
    options.ConnectionStrings.Add(new ConnectionStringOptions
    {
        ConnectionString = _configuration.GetConnectionString("EcfSqlConnection"),
        Name = "EcfSqlConnection"
    });
});

This is now automatically done in the .AddCommerce() extension method.

Native language names should be used in the language selection component. For example, the chosen languages section showed English and Swedish instead of English and Svenska.

EPiServer.Commerc_e has a dependency to _EPiServer.Commerce.UI.CustomerService which has a dependency to EPiServer.Telemetry.UI.Core 2.0.0 which does not exist, which caused warnings when you restored.

When searching in the Contact list the "Rows per page" setting was reset to the default value of 10.

Promotion caching worked incorrectly with an anonymous user. A discount was applied for anonymous user when it should not have been applied.

The Email field Validator allowed email addresses with two full stops in the domain. For example:

paula.sample@borbia..ie
vanet@google..com
menikor@yahoo..co..in

GetDataList returned HtmlContent instead of string.

When you uploaded an image with alpha channel != 0, you saw black instead of transparent.

FileSystemWatchers watched zip files that were related to shell modules. However, since the zip files do not change during runtime of the application, it was unnecessary to use the FileSystemWatcher. So now, FileSystemWatcher is disabled by default. You can enable it if you need it.

When you created your own EmptyWastebasketJob, gave it a new guid and started the job in admin, the job had a translated name instead of the one that was set by the LanguagePath = "/admin/databasejob/wastebasket" attribute. Even if you removed the attribute and changed the DisplayName, the job still had the translated name.

If you then removed all attributes except for guid and DisplayName, and gave the job a new guid, it resulted in no new job registered; just the same job with the same name.

[Netcore] A NullReferenceException exception occurred when adding MapControllerRoute, when the search result should have been returned.