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.
Sounds like your project has global using directives or the project file has <ImplicitUsings>enable</ImplicitUsings>.
Create a LINQPad script with the following content:
global using System;
global using System.Linq;
global using System.Collections.Generic;
global using System.IO;
global using System.Net.Http;
global using System.Threading;
global using System.Threading.Tasks;
and save it to a file such as "implicits.linq". You can add any other imports that your project needs. Note that this script must have the language set to "C# Statements".
Then in your main script, include this script as follows:
@JoeAlbahari Thanks for the macOS version, LinqPad was the only thing I missed from my Windows days!
Regarding the feature delta between the Windows and the macOS versions: I see the Roslyn Syntax Tree is planned (great!), but I don't see the mention of the native assembly support (then again, it's not in the "won't ever happen" section, so there's hope )? I understand that both are relatively niche but for my use-cases, they are very welcome indeed. It's understood that for macOS, the only ISA worth mention is the Apple Silicon, but I assume you're not producing the assembly yourself, you delegate to the .NET itself? Thanks in advance for any info!
One small thing: would it be possible to implement the support for the "system" theme? Some people, myself included, use light themes during the day when there's a lot of the natural light but switch to the dark theme in the evening/night. This should be relatively straightforward from what I can gather. And yeah, clicking once/twice per day on the theme selector isn't a big deal, but I'd really appreciate not having to do this if it's not a big bother.
The short answer is that supporting Intel processors is more work than it appears. There are just a few people asking for it - not enough to justify the investment, especially given that architecture is dying.
Automatically switching themes is on the TODO list. If you're able to send me the code, it will speed this up. gpt-4o or sonnet gets you most of the way there, but it appears there's some fiddling to do around the call to CFNotificationCenterAddObserver.
The short answer is that supporting Intel processors is more work than it appears.
Apologies, we may have a misunderstanding - I am not asking for Intel support (personally couldn't care less), that ISA is dead to me: I was asking for the ARM (Apple Silicon) assembly support
Automatically switching themes is on the TODO list.
If you're able to send me the code, it will speed this up
Well, a short exploration shows that for the default Avalonia MVVM app, there's nothing to do: the template produces the App.axaml with the following snippet (lots of difficulties with XAML markup in the post, apologies for the small snippet) Application markup
....
RequestedThemeVariant="Default">
<!-- "Default" ThemeVariant follows system theme variant. "Dark" or "Light" are other available options. --
The key appears to be the RequestedThemeVariant. I tried running the empty app and it did react to the system theme change on its own.
OTOH, you seem to be using XPF which is a paid product and may follow slightly different "rules". Since I don't have the license for XPF, I cannot verify whether a simple default app works OOB or not.
@JoeAlbahari said:
Yes, in a build early March if there are no blocking issues
Outstanding! Once that and Roslyn Visualizer are in, there will literally be no other tool in the .NET ecosystem comparable to what LINQPad does. For advanced tinkering and experimentation, it will be unmatched. Thank you so much.
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.
this is the best day of my life been waiting for 4 years.
ty so far it is working very good
@JoeAlbahari
It is soooo snapy. It works greattttt thanks
When I use #load for .cs files I get reference errors
...: CS0246 The type or namespace name 'List<>' could not be found
Sounds like your project has
global usingdirectives or the project file has<ImplicitUsings>enable</ImplicitUsings>.Create a LINQPad script with the following content:
and save it to a file such as "implicits.linq". You can add any other imports that your project needs. Note that this script must have the language set to "C# Statements".
Then in your main script, include this script as follows:
@JoeAlbahari Thanks for the macOS version, LinqPad was the only thing I missed from my Windows days!
Regarding the feature delta between the Windows and the macOS versions: I see the Roslyn Syntax Tree is planned (great!), but I don't see the mention of the native assembly support (then again, it's not in the "won't ever happen" section, so there's hope
)? I understand that both are relatively niche but for my use-cases, they are very welcome indeed. It's understood that for macOS, the only ISA worth mention is the Apple Silicon, but I assume you're not producing the assembly yourself, you delegate to the .NET itself? Thanks in advance for any info!
One small thing: would it be possible to implement the support for the "system" theme? Some people, myself included, use light themes during the day when there's a lot of the natural light but switch to the dark theme in the evening/night. This should be relatively straightforward from what I can gather. And yeah, clicking once/twice per day on the theme selector isn't a big deal, but I'd really appreciate not having to do this if it's not a big bother.
Thanks again and keep up the good work.
The short answer is that supporting Intel processors is more work than it appears. There are just a few people asking for it - not enough to justify the investment, especially given that architecture is dying.
Automatically switching themes is on the TODO list. If you're able to send me the code, it will speed this up. gpt-4o or sonnet gets you most of the way there, but it appears there's some fiddling to do around the call to CFNotificationCenterAddObserver.
Apologies, we may have a misunderstanding - I am not asking for Intel support (personally couldn't care less), that ISA is dead to me: I was asking for the ARM (Apple Silicon) assembly support
Good to know, thanks.
Challenge accepted
Well, a short exploration shows that for the default Avalonia MVVM app, there's nothing to do: the template produces the
App.axamlwith the following snippet (lots of difficulties with XAML markup in the post, apologies for the small snippet)ApplicationmarkupThe key appears to be the
RequestedThemeVariant. I tried running the empty app and it did react to the system theme change on its own.OTOH, you seem to be using XPF which is a paid product and may follow slightly different "rules". Since I don't have the license for XPF, I cannot verify whether a simple default app works OOB or not.
Hope this helps.
Thanks - I'll see whether I can hook into this.
Nice. The assembly question seems to have fallen through the cracks - there is a plan to support ARM assembly on a modern macOS, yes?
Yes, in a build early March if there are no blocking issues
Outstanding! Once that and Roslyn Visualizer are in, there will literally be no other tool in the .NET ecosystem comparable to what LINQPad does. For advanced tinkering and experimentation, it will be unmatched. Thank you so much.