Capture screenshot Including Semitransparent windows in .NET

Question

I would like a relatively hack-free way to do this, any ideas? For example, the following takes a screenshot that doesn't include the semi-transparent window:

Public Class Form1     Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Shown         Text = "Opaque Window"         Dim win2 As New Form         win2.Opacity = 0.5         win2.Text = "Tranparent Window"         win2.Show()         win2.Top = Top + 50         win2.Left = Left() + 50         Dim bounds As Rectangle = System.Windows.Forms.Screen.GetBounds(Point.Empty)         Using bmp As Bitmap = New Bitmap(bounds.Width, bounds.Height)             Using g As Graphics = Graphics.FromImage(bmp)                 g.CopyFromScreen(Point.Empty, Point.Empty, bounds.Size)             End Using             bmp.Save("c:\temp\scn.gif")         End Using         Process.Start(New Diagnostics.ProcessStartInfo("c:\temp\scn.gif") With {.UseShellExecute = True})     End Sub End Class 

Either my google-fu really sucks or this is not as easy as it sounds. I'm pretty sure why this is happening because of the way the video driver would have to separate the memory to make this work, but I don't care why it doesn't work, I just want to do it without...
* print-screen key hacks
* 3rd party software
* SDK functions are OK but I'll upvote every object owned by the user that can show me it in pure framework (Just kidding but it would be nice).

If This is the only way to do it, how to I do that in VB?
1M thanks.

Answer 1

Forms that have the TransparencyKey or Opacity property set are so-called layered windows. They are shown using the "overlay" feature of the video adapter. Which make them being able to have their transparency effects.

Capturing them requires turning on the CopyPixelOperation.CaptureBlt option in the CopyFromScreen overload that accepts the CopyPixelOperation argument.

Unfortunately, this overload has a critical bug that prevents this from working. It doesn't validate the value properly. Still not fixed in .NET 4.0. There is no other good fix but fall back to using P/Invoke to make the screen shot. Here's an example:

using System; using System.Drawing; using System.Windows.Forms; using System.Runtime.InteropServices;  namespace WindowsApplication1 {   public partial class Form1 : Form {     public Form1() {       InitializeComponent();     }     private void button1_Click(object sender, EventArgs e) {       Size sz = Screen.PrimaryScreen.Bounds.Size;       IntPtr hDesk = GetDesktopWindow();       IntPtr hSrce = GetWindowDC(hDesk);       IntPtr hDest = CreateCompatibleDC(hSrce);       IntPtr hBmp = CreateCompatibleBitmap(hSrce, sz.Width, sz.Height);       IntPtr hOldBmp = SelectObject(hDest, hBmp);       bool b = BitBlt(hDest, 0, 0, sz.Width, sz.Height, hSrce, 0, 0, CopyPixelOperation.SourceCopy | CopyPixelOperation.CaptureBlt);       Bitmap bmp = Bitmap.FromHbitmap(hBmp);       SelectObject(hDest, hOldBmp);       DeleteObject(hBmp);       DeleteDC(hDest);       ReleaseDC(hDesk, hSrce);       bmp.Save(@"c:\temp\test.png");       bmp.Dispose();     }      // P/Invoke declarations     [DllImport("gdi32.dll")]     static extern bool BitBlt(IntPtr hdcDest, int xDest, int yDest, int     wDest, int hDest, IntPtr hdcSource, int xSrc, int ySrc, CopyPixelOperation rop);     [DllImport("user32.dll")]     static extern bool ReleaseDC(IntPtr hWnd, IntPtr hDc);     [DllImport("gdi32.dll")]     static extern IntPtr DeleteDC(IntPtr hDc);     [DllImport("gdi32.dll")]     static extern IntPtr DeleteObject(IntPtr hDc);     [DllImport("gdi32.dll")]     static extern IntPtr CreateCompatibleBitmap(IntPtr hdc, int nWidth, int nHeight);     [DllImport("gdi32.dll")]     static extern IntPtr CreateCompatibleDC(IntPtr hdc);     [DllImport("gdi32.dll")]     static extern IntPtr SelectObject(IntPtr hdc, IntPtr bmp);     [DllImport("user32.dll")]     public static extern IntPtr GetDesktopWindow();     [DllImport("user32.dll")]     public static extern IntPtr GetWindowDC(IntPtr ptr);   } } 

Fwiw, a later Windows version provided a workaround for this bug. Not exactly sure which, I think it was Win7 SP1. The BitBlt() function will now do what you want if you pass only the CopyPixelOperation.CaptureBlt option. But of course that workaround wasn't applied retro-actively to earlier Windows versions so you can't really depend on it.