Forum Widgets
Latest Discussions
.NET
Hi everyone! 👋 I’m new to this community and currently learning .NET App Development. I’m really excited to join and connect with developers here. I believe the discussions and knowledge shared in this community are very valuable, especially for beginners like me. I’m looking forward to learning from your experiences and improving my development skills. If you have any tips, recommended resources, or advice for someone starting with .NET, I would really appreciate it. Happy to be part of this community! 😊
Windows Forms user control layout issues at runtime
I'm hoping the good folls of this community can help me figure out what's going on with a Windows Forms user control that I created and am trying to use. I created a user control that represents a single band of a parametric equalizer. In the designer, the control looks like this: When I debug the control in the Test Container, things look good: If we take a look at the actual PEQ application that will use the control, things still look OK in the designer: It's only when I fire up the application that things go... awry: What happened to all the TextBoxes? And the ComboBoxes? I''ve got a feeling that the fix for this is something really simple, and I'm going to feel like a complete idiot for not figuring out the obvious. Can anyone tell me what my dumb self did wrong?
WPF application becomes unresponsive after plugging/ unplugging USB device supporting pen events
I've run across an issue on Windows 10 and 11 where WPF apps seem to become unresponsive when unplugging or plugging in a USB device that registers as an input device that can receive touch/stylus events. This can be seen by creating a basic WPF app in Visual Studio, running it, and then adding/removing one of these devices. I used Spy++ to see which messages the app was receiving. I saw a number of messages I was expecting to see - WM_DEVICECHANGE, WM_POINTERDEVICECHANGE, as well as 0x02C8 or 0x02C9 (WM_TABLET_ADDED or WM_TABLET_DELETED, respectively). However, after this, thousands (or sometimes tens of thousands) of messages were sent to a window belonging to the app that is at (0,0) with dimensions 0x0. Its caption is "OLEChannelWnd". The messages are mostly the same: They're all posted to the window The message ID is 0x0400 (WM_USER + 0) The wParam is always the same (0x0000BABE) The lParam varies each time I restart the WPF app, but they seem to settle on a small number of values - for example, the last time I tried this, I saw 0x05D08BB0 4-6 times, then 0x0D1B8E98 a dozen or more times, then 0x0D1B7B90 several times, and so on. During these messages, the app would become unresponsive for as long as these messages were posted. This could take upwards of 5- 10 minutes before recovering, and sometimes would result in a crash from the app running out of memory. After doing research online, I found some posts that talked about a possible issue in the PenThreadWorker thread - that it could be running into some kind of deadlock when initializing certain objects. I also found several posts that mentioned disabling the stylus & touch events by setting "Switch.System.Windows.Input.Stylus.DisableStylusAndTouchSupport". I can add this to the app.config for my app as follows: <runtime> <AppContextSwitchOverrides value="Switch.System.Windows.Input.Stylus.DisableStylusAndTouchSupport=true" /> </runtime> or, equivalently, I can do the following during application startup: AppContext.SetSwitch("Switch.System.Windows.Input.Stylus.DisableStylusAndTouchSupport", true); This does fix the issue - I don't see these WM_USER messages being sent to the app, and as such the app becomes immediately responsive once the device is plugged/unplugged. However, one of the WPF apps that I'm working with (i.e. not the simple test app) needs to process tablet events, so this setting can't be used there. Furthermore, it can only be set either in app.config or during application startup - any calls to it after that are ignored. I've tried this with .NET 4.5.1, .NET 4.6 (which is required to use the code-based method) as well as .NET 4.8.1, but in all cases I see this same result. As mentioned, I know this isn't an issue unique to my app since I'm able to reproduce this issue by creating a basic WPF app and following the same steps. Additionally, I observed the same issue with other test applications I've found online while trying to troubleshoot this issue. Interestingly, I have observed this within Microsoft's own Visual Studios 2017 (which is what I'm using for development) and have found a few other threads online from other people running into the same problem with their apps. I have also tried updating to later Visual Studios versions for development of my app, but this doesn't solve the issue either. Finally, I followed this post from Microsoft regarding https://learn.microsoft.com/en-us/dotnet/desktop/wpf/advanced/disable-the-realtimestylus-for-wpf-applications and still was unable to fix the issue.
MAUI Android API 35: Action Bar still visible despite NavBarIsVisible=False
Before API 35 it was ok. I am using .NET 9, Android API 35, using Shell, etc. I have tried: Shell.NavBarIsVisible, NavigationPage.HasNavigationBar, theme tweaks, etc. What’s still happening: Title bar remains visible on Android.
WPF App on Windows Server (RDP) – Error Sometimes When Opening New Window
Hi everyone, I have a WPF app that runs from a network drive. It works fine on Windows 11 at the office. But when users run it through Remote Desktop on a Windows Server 2019 virtual machine (using the exact same .exe from the same network drive location), some of them get an error when opening a new window. The app starts normally, but the error happens only when opening another window — and not for every user. Strangely, the next day the same user can open the app and use it normally again without changing anything. Has anyone seen this before or know how to fix it? I’ve also attached: A screenshot of the error message The function that causes the error Thanks a lot!
