Most likely, it will be related to LINQPad including newer versions of some of those dependencies. In any case, the driver seems to work correctly now, and scripts that reference the NuGet package will work when Microsoft.Data.SqlClient 6.0.0 becomes RTM.
Note that as an alternative to referencing "~/Library/Application Support/LINQPad/8.101.8/L2S/Microsoft.Data.SqlClient.dll", you can tick the checkbox "Reference LINQ-to-SQL assemblies" in Query Properties > Advanced.
@gordy - can I get you to do one more thing: try again under .NET 6 (choose .NET 6 in LINQPad's .NET dropdown on the toolbar - you may need to install .NET 6). If this works correctly with the Microsoft.Data.SqlClient 5.2.x NuGet package reference, we likely have a more serious problem (a bug in Microsoft.Data.SqlClient which we need to report to Microsoft). If this is the case, we'll need a MRE that will work the dotnet command-line:
Run this with dotnet run - with TargetFramework set to net8.0 or net9.0, and then again with net6.0. If it fails under .net 8 but succeeds under .net 6, we have the info we need for MS to fix it.
I installed this on my M2 Macbook Pro running latest Sonoma and it crashes on startup. I have submitted a bug report. I tried to enter my email address into the crash report form but I only managed to get the first letter or two in the box. The error was something about nto being able to give focus to the application.
I should say I am using VoiceOver. I used LinqPad for years a good while ago o Windows. Since then I've moved to Mac and gone blind (not related). So I was excited to hear that LinqPad had come to Mac.
So I'm wondering if it is accessible with screen readers?
@JohnC - I can reproduce that error with VoiceOver, but the bad news is that after getting past that there are a whole bunch of other issues, including the editor, which doesn't seem to support screen readers at all.
Finally we got this.!!!
i updated my subscription to 8.
I would like to thank the entire team who contributed to the development, which enabled me to make the development at the speed of light as before.
Comments
there are a lot of differences, see attached the assembly resolution log from both runs.
Most likely, it will be related to LINQPad including newer versions of some of those dependencies. In any case, the driver seems to work correctly now, and scripts that reference the NuGet package will work when Microsoft.Data.SqlClient 6.0.0 becomes RTM.
Note that as an alternative to referencing "~/Library/Application Support/LINQPad/8.101.8/L2S/Microsoft.Data.SqlClient.dll", you can tick the checkbox "Reference LINQ-to-SQL assemblies" in Query Properties > Advanced.
@gordy - can I get you to do one more thing: try again under .NET 6 (choose .NET 6 in LINQPad's .NET dropdown on the toolbar - you may need to install .NET 6). If this works correctly with the Microsoft.Data.SqlClient 5.2.x NuGet package reference, we likely have a more serious problem (a bug in Microsoft.Data.SqlClient which we need to report to Microsoft). If this is the case, we'll need a MRE that will work the dotnet command-line:
SqlClientTest.csproj:
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>net8.0</TargetFramework> <ImplicitUsings>enable</ImplicitUsings> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.Data.SqlClient" Version="5.2.2" /> </ItemGroup> </Project>Program.cs:
using Microsoft.Data.SqlClient; Console.WriteLine ($"Using {typeof (SqlConnection).Assembly.Location}"); try { new SqlConnection ("Data Source=(server);initial catalog=master;Integrated Security=SSPI;TrustServerCertificate=true").Open(); Console.WriteLine ("Success"); } catch (SqlException ex) { Console.WriteLine (ex.Message); }Run this with dotnet run - with TargetFramework set to net8.0 or net9.0, and then again with net6.0. If it fails under .net 8 but succeeds under .net 6, we have the info we need for MS to fix it.
I installed this on my M2 Macbook Pro running latest Sonoma and it crashes on startup. I have submitted a bug report. I tried to enter my email address into the crash report form but I only managed to get the first letter or two in the box. The error was something about nto being able to give focus to the application.
I should say I am using VoiceOver. I used LinqPad for years a good while ago o Windows. Since then I've moved to Mac and gone blind (not related). So I was excited to hear that LinqPad had come to Mac.
So I'm wondering if it is accessible with screen readers?
@JohnC - I can reproduce that error with VoiceOver, but the bad news is that after getting past that there are a whole bunch of other issues, including the editor, which doesn't seem to support screen readers at all.
@Joe - thanks very much for trying. I had a feeling it might have been a long shot.
Finally we got this.!!!
i updated my subscription to 8.
I would like to thank the entire team who contributed to the development, which enabled me to make the development at the speed of light as before.
Is the current version of debug unavailable?
The debugger is not yet available (see release notes or 'What's New').
Loving this support for Mac, thanks Joe; appreciate the effort.