Maxim Korsukov

After dependencies upgrade to latest versions, new .NET types seem to work fine with Dapper. ``` ``` And custom type handlers `SqlMapper.TypeHandler` are not used by Dapper any more.

Same issues for me. I posted two clean experiments in the referenced issue.

@GonzaloVisma Do you use the `System.Data.SqlClient` or `Microsoft.Data.SqlClient` in a combination with Dapper? I have been using the first one with the same workaround you listed above. But recently I...

@GonzaloVisma Here is my current setup for data-related project: ```xml ```

I experience the same issue. Here is a settings page:  But any automated / generated result is in UPPERCASE casing. ```sql ALTER TABLE [dbo].[Bookkeeping] DROP CONSTRAINT [PK_Bookkeeping_LeadId] WITH (...

I made a couple experiments on clean virtual machines. **Experiment 1** - Linux Mint Cinnamon `21.2` - .NET `8.0.103` - VS Codium `1.87.2` - C# extension (by muhammad-sammy) `2.22.3` -...

Same issue after updating C# extension to `2.23.15`. ``` OmniSharp server started with .NET 8.0.202 Path: /home/max/.vscode/extensions/ms-dotnettools.csharp-2.23.15-linux-x64/.omnisharp/1.39.11-net6.0/OmniSharp.dll PID: 43852 ```

Dear OmniSharp team, were you able to reproduce the issue? Editing, autocomplete and refactoring features are very important for successfull programming. Maybe there is a workaround available?

Issue still exists after upgrade to `2.28.11`.

Looks like OmniSharp is trying to load `internal` [PooledObject](https://github.com/dotnet/razor/blob/main/src/Shared/Microsoft.AspNetCore.Razor.Utilities.Shared/PooledObjects/PooledObject%601.cs) type from the `Microsoft.AspNetCore.Razor.Utilities.Shared` assembly using reflection. Maybe there is an incorrect referencing of assembly or its version? Here are findings...