Ensuring that application is independent of users' screen resolution - c#

Is there any easy way to run an application created in C# on Visual Studio 2005 on any different PC, regardless of its screen resolution?

Screen resolution?
Windows Forms in .NET 2.0 has some mechanisms for dealing with different DPI and it has a better layout system than in .NET 1.1. In general, use layout panels like FlowLayoutPanel, TableLayoutPanel, etc instead of fixing your controls at X/Y coordinates and you'll have a much easier time dealing with different window sizes.
If you can use WPF which I don't recall being applicable to Visual Studio 2005, then you have much more options for resolution independence. The DPI issue goes away and WPF has features such as ViewBox that lets you scale an entire window or control uniformly.

Related

Win Form Design Change as the screen resolution Change

We are developing a WinForm application. We have different resolution monitors when designing win form on low resolution and viewing on high resolution, the positions are changed and they appear merged. Could anyone suggest how to resolve this issue. Thanks in advance
We are using VS2102 For development. And Framework is 4.0
If you are starting with development on Windows Desktop you can also explore on WPF, it has a higher initial learning curve than WinForms, but is far more extensible.
If you are still going for WinForms, take a look at dynamically controlling the sizing from this answer https://stackoverflow.com/a/6575311/5788393

VS2013 - Issue with high DPI screen and WinForms

I built an application on a computer with normal DPI size. It is a WinForms application with many forms and custom controls. When I open the project on my Lenovo Yoga 900 with high DPI it looks good in Visual Studio 2013 but when I run the application some parts are off screen.
Even worse is when I open the application after a change on my "normal DPI computer". Most of the controls are scaled up, margins and paddings are scaled too.
With other words my forms are messed up. I've read about the AutoScaleMode which is set to Font. Even I change that property there are not realy noticable changes.
Any suggestions how I can handle that problem? Or does someone have similar experiences/issues?

Scaling to different resolutions in C# with Visual Studio

I am creating a windows form application in Visual Studio Community 2015. I've built the interface on a 1080p monitor and anchored controls so that when the form is resized, things stay where I want and stretch how I want.
The problem is, I need to try and get this to work on a monitor that is 1024 x 768 and the minimum size of my application is actually larger than that. This causes controls to overlap due to the anchoring and some controls aren't shown at all (they are cut off).
Is there anyway I can easily scale my application to different resolutions automatically?

Do I have to handle HiDPI capabilities within my source code, or is it provided by .Net resp. Windows?

I'm working on a Software using C# and .Net 4.5. I started the project on an older machine with a dpi scaling of 100%. On my new machine I had to setup a scaling of 200% because of the high res display.
Within the Visual Studio Designer the Gui of the software renders perfectly:
Gui within the Designer.
The Gui of the compiled software renders bad: Gui in compiled software.
My expectation is, that because I'm using only .Net Gui Elements/Controls and no self designed gui elements, windows should handle the scaling without any problems. But as I see, windows doesn't.
Do I have to enable a HiDPI Option in the project settings in Visual Studio, or do I have to handle HiDPI within my code?
By default, most Windows Forms applications aren't DPI aware. In fact, most Windows applications aren't DPI aware. So you need to opt-in to DPI-awareness in your application manifest:
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"
xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
<asmv3:application>
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
<dpiAware>true</dpiAware>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
Since DPI-awareness is per-process, the VS designer has no choice on the matter - it runs within Visual Studio, which is DPI aware.
Make sure everything works properly with both low-DPI and high-DPI, though. DPI aware means "I'm going to handle all DPI scaling correctly, no need to fake it for me; thanks." Hopefully, you've designed your forms with either proper autoscaling and layouting, or using device independent units rather than pixels :)
When your application doesn't declare being DPI aware, Windows assumes you are a legacy application that didn't handle DPI properly. So to prevent issues, it pretends that you're actually rendering to a display that's smaller - in your case, half the size, and then upscales the resulting surface back to proper size. This causes the blurriness, especially with text, but ensures that everything has the proper size and ratios - e.g. you don't get buttons smaller than the text inside them, or controls that overlap.
Both Windows Forms and WPF have great support for proper handling of DPI, if you use the correct layouting approaches, so .NET is definitely DPI-aware-capable. But both are also quite capable of being DPI-unaware, and most applications still ignore DPI issues, so the default is the same as for any other Windows application. Since there's no "legacy WPF" applications, and the simplest way to do WPF is also DPI aware, the default project template for WPF already includes a manifest that declares DPI awareness, so I assume you created your project in Windows Forms :) In fact, given how Windows evolves nowadays, you probably want to have an assembly manifest anyway, to properly manage all the compatibility features :)
For extra bonus, there's even more issues when you have multiple monitors with different DPI - to declare proper support for that, you'd use <dpiAware>true/PM</dpiAware>. This is only available on Windows 8.1+ and it can be quite tricky to implement correctly.
It worked for me by doing this:
Click on the mremoteng desktop link properties
Go to the compatibility tab
Under the "Settings" section check "Override high DPI scaling behavior"
Choose "Application" the selectable list.
That's it, I hope it works for you too.

Displaced controls in windows forms .net framework

I have a strange problem. I have designed a windows form application in c# and .net framework 3.5. In the runtime, the form and its controls are fine in all the computers except my laptop, where the controls are not in the correct positions.
If I design the form from scratch on my laptop with correct positioning it will result in an invalid shape for other computers.
My efforts:
If I run the windows in Safe Mode the form size and control positions
are correct.
I have uninstalled the Video Driver and used default windows version but the problem still persists.
I used different frameworks like 2.0 and 4.0, and different Visual Studios versions and they all have the same problems.
Actually all the .net framework product from all the companies indicate the same issue.
My computer Settings:
Laptop 1557 Studio DELL
Graphic ATI Radeon HD 4500
When the text size is artificially increased to 125% text and controls that are rather closely placed will wrap around the form and push everything down/over. If this is something you intend to support, you'll simply have to redesign your form to handle the different enlargement levels you care to support and test those enlarged text modes in your app until you're satisfied with their appearance. It's not something you can strictly control, since increased text size is an accessibility feature.
I assume it is due to a screen resolution differences. I believe that the actual location of the controls is identical in both cases, in one the screen is "larger" and therefor your controls appear in a different position on the screen.
try Designing forms to work on different resolutions and aspect ratios on Windows CE
Another thing you can (and should) do is work with WPF, which is the new way to build user interfaces for windows.
I've found a workaround just now.
In the display settings of Windows 7 I have changed the Text size from 125% to 100%. Everything is smaller but in accurate positions and sizes.
Still wondering how it works!!

Categories