David McClelland

Our company is a Microsoft (SQL Server / C#) shop, so if we could get .NET support that would enable us to look into doing a POC with Oso.

> Removing the refactoring and reason for changing to const enums (so they are replaced at compile time with the numeric values for minification). @MSNev - does this mean this...

Any ETA on when Static Web Apps will be available in additional regions? Like southcentral US, northcentral US...

@rohancragg - Even after installing Python as you suggested, I still get the following error message from `gyp`: ``` npm ERR! gyp ERR! find VS ************************************************************** npm ERR! gyp ERR!...

Any updates @kccarter76 ?

@maumar I appreciate that workaround! And it did work for me, but we would prefer to not have to make this change throughout the codebase for every usage of StartsWith/EndsWith/Contains....

**Side note:** downgrading back to Microsoft.EntityFrameworkCore.SqlServer v7.0.18 produces the following SQL, which is less readable, but it does work with Azure Synapse without any changes to our codebase: ```sql SELECT...

Can I put in a request for a config/option/setting to disable the ESCAPE clause from being generated? I know you may not have very many EF users that query Azure...

Synapse does have some other "unique" syntax requirements, particularly related to paging as mentioned here: [Query: Bring back support for UseRowNumberForPaging](https://github.com/dotnet/efcore/issues/16400#issuecomment-668109814) Reference: [Transact-SQL features supported in Azure Synapse SQL](https://learn.microsoft.com/en-us/azure/synapse-analytics/sql/overview-features#query-language)