No Dark Mode

[sindizzy]

I tried all the steps and it didn't take. I even forced Dark and nothing.
Do you have a test harness where it shows the steps.
Maybe I missed something.

I'm running Windows 10 build 17763 (also known as the October 2018 Update or version 1809).

[ryanbester]

Hello,

Could you please provide me with some more details of your development environment (i.e. .NET version, C# or VB). The library has been tested to work with .NET Core and one of the recent Framework versions, but I'm not sure how well it'll work with older versions.

One thing to try is to make sure your application Startup and form WndProc events are firing correctly. A way to do this is just to add a Console.WriteLine() inside the function somewhere.

Also, if you're using a custom Windows theme it may not support 1809 dark mode.

[sindizzy]

My project is written in VB.NET against the .NET 4.6 Framework which is what you set the DarkMode.dll as well. Using VS2019 for the compile. I don't believe I have any custom Windows theme that are active. I also stepped through the code as it was being run and it seemed to be firing all the routines in your DLL.

If you have a simple project that you know works under Framework that would probably help me.

[ryanbester]

I will upload a project using the library to my GitHub as soon as possible. The only issue is I'm using the latest version of Windows 10, not 1809, but it should at least rule out whether it is the Windows version causing the issue or not.

[sindizzy]

Great. Thanks.

[sindizzy]

Just wanted to circle back to see if there was any progress. Is there a repo that uses this DLL that I can test?

[ryanbester]

Sorry, I haven't had access to my Windows machine until now.

I tried creating a sample project that used .NET Framework but I couldn't get the DarkMode library to work. NuGet said it was the wrong version and when I tried compiling and referencing the DLL manually it just wouldn't compile.

I created a sample project using .NET 6.0 here. I have tested this and it appears to work. It makes use of the NuGet package so should compile straight away after cloning.

Please let me know how this sample project works.

[sindizzy]

That is so odd. I must have something on that is in conflict.
Here is what this looks like on 2 of my machines:

[ryanbester]

Do the build-in applications, such as File Explorer and Settings display in dark mode?

[sindizzy]

Yes they are in dark mode:

[ryanbester]

Apologies for the late response, I've just got back from vacation. The main thing I could suggest is making sure your system is up to date. Previously you stated you were using version 1809, which is getting pretty outdated now.

If for any reason you need to use 1809 (e.g. company policy, which I understand), I can spin up a VM and investigate what could be causing the dark mode not to function; however, it may be a bit of a challenge to get hold of an 1809 ISO.

There is one more thing you could try though. Some third-party apps make use of dark mode (I believe paint.NET does). Depending on how these apps behave with your system dark mode setting, it could help in finding where the problem lies; whether it's my dark mode library or Windows.

[sindizzy]

I use paint.net so let me try that and I will report.

[sindizzy]

In this snapshot I am using Win10 Enterprise. I will test also with Win10 retail.

[sindizzy]

Here is my personal PC

[ryanbester]

I've just realised, I don't think I ever updated the library to work with 21H2 (19044). I have just pushed an update which should support this version (commit be1ef79). It'll be live on NuGet shortly.

[sindizzy]

So still no-go. But it did dawn on me after looking at the code...is this only for 32-bit? I run 64-bit on all my machines.
This piece of code says:

    ' Assumes wParam is on 32 bit. Different on 16 bit and 64 bit.
    <DllImport("user32.dll", CharSet:=CharSet.Unicode, SetLastError:=True)>
    Private Function SendMessage(ByVal hWnd As IntPtr, ByVal msg As UInt32, ByVal wParam As Int32, ByVal lParam As Int32) _
        As Int32
    End Function

So just wondering if its a bitness issue.