Skip to main content

How to change Windows wallpaper from .NET

Din core-ul de .NET, nu avem nici o posibilitate sa schimbam imaginea de fundal a sistemului de operare sau sa schimbam modul in care se afiseaza - in mod direct. Ca sa putem face acest lucru, putem sa schimbam valorile din registri care stocheaza modul in care se afiseaza imaginea de fundal. Iar imaginea de fundal se schimba apeland direct API sistemului de operare.
Sub directorul userului curent, in path-ul "ControlPanel\Desktop" o sa gasim cheile necesare pentru a seta modul in care se afiseaza imagina de fundal.
Cheia WallpaperStyle impreuna cu TileWallpaper ne permite sa setam felul in care se centreaza imaginea. Urmatarele combinatii de valori se pot face:
  • (WallpaperStyle = 2, TileWallpaper = 0) - se face stretch la imagine ca sa acopere tot spatil ecranului
  • (WallpaperStyle = 0, TileWallpaper = 1) - se face tile pe imagine pana cand ecranul este umplut
  • (WallpaperStyle = 0, TileWallpaper = 0) - imaginea se afiseaza centrat
Aceste valori se pot seta in felul urmator
public enum Style
{
Tiled,
Centered,
Stretched
}
...
RegistryKey key = Registry.CurrentUser.OpenSubKey(@"Control Panel\Desktop", true);
switch (style)
{
case Style.Stretched:
key.SetValue(@"WallpaperStyle", 2.ToString());
key.SetValue(@"TileWallpaper", 0.ToString());
break;
case Style.Centered:
key.SetValue(@"WallpaperStyle", 1.ToString());
key.SetValue(@"TileWallpaper", 0.ToString());
break;
case Style.Tiled:
key.SetValue(@"WallpaperStyle", 1.ToString());
key.SetValue(@"TileWallpaper", 1.ToString());
break;
}
Am vazut cum putem seta ca imaginea de fundal sa se afiseze in diferite moduri. Urmatorul pas este sa vedem cum putem sa setam din cod imaginea de fundal. Pentru acest lucru trebuie sa facem apel la API de windows si sa ne definim urmatoarea metoda:
[DllImport("user32.dll", CharSet = CharSet.Auto)]
static extern int SystemParametersInfo(int uAction, int uParam, string lpvParam, int fuWinIni);
Prin intermediul acestei metode putem seta sau obtine valoarea parametriilor din sistemul de operare. Actiunea care permite setarea imaginii din fundal are valoare 20.
SystemParametersInfo(
20, // Actiunea pentru setarea imaginii de fundal.
0,
imageFilePath, // Locatia spre imaginea noastra
0x01 | 0x02);

Enjoy!

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see