Geek Answers Handbook

C #: comctl32.dll version 6 in the debugger

I am using WindowsAPICodePack for TaskDialog. When I try to show the dialog, it says that it needs to download version 6 of comctl32.dll. So I added version 6 to app.manifest and tried to run it. Not lucky yet. I went to the Debug folder and ran the program without Visual Studio, and it works fine. I assume Visual Studio is not using a manifest file ... I was wondering if there is a way to do this.

+6
c # visual-studio-2008 winapi comctl32
source share
4 answers

Robpol86, your code throws SEHExceptions, because the signatures for ActivateActCtx and DeactivateActCtx are incorrect. You should use UIntPtr instead of uint for lpCookie.

Therefore, the correct code for EnableThemingInScope.cs would be:

 using System; using System.IO; using System.Runtime.InteropServices; using System.Security; using System.Security.Permissions; using System.Windows.Forms; namespace Microsoft.WindowsAPICodePack.Dialogs { /// http://support.microsoft.com/kb/830033 /// <devdoc> /// This class is intended to use with the C# 'using' statement in /// to activate an activation context for turning on visual theming at /// the beginning of a scope, and have it automatically deactivated /// when the scope is exited. /// </devdoc> [SuppressUnmanagedCodeSecurity] internal class EnableThemingInScope : IDisposable { // Private data private UIntPtr cookie; private static ACTCTX enableThemingActivationContext; [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Reliability", "CA2006:UseSafeHandleToEncapsulateNativeResources")] private static IntPtr hActCtx; private static bool contextCreationSucceeded = false; public EnableThemingInScope(bool enable) { cookie = UIntPtr.Zero; if (enable && OSFeature.Feature.IsPresent(OSFeature.Themes)) { if (EnsureActivateContextCreated()) { if (!ActivateActCtx(hActCtx, out cookie)) { // Be sure cookie always zero if activation failed cookie = UIntPtr.Zero; } } } } ~EnableThemingInScope() { Dispose(); } void IDisposable.Dispose() { Dispose(); GC.SuppressFinalize(this); } private void Dispose() { if (cookie != UIntPtr.Zero) { try { if (DeactivateActCtx(0, cookie)) { // deactivation succeeded... cookie = UIntPtr.Zero; } } catch (SEHException) { //Hopefully solved this exception } } } [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Reliability", "CA2002:DoNotLockOnObjectsWithWeakIdentity")] private static bool EnsureActivateContextCreated() { lock (typeof(EnableThemingInScope)) { if (!contextCreationSucceeded) { // Pull manifest from the .NET Framework install // directory string assemblyLoc = null; FileIOPermission fiop = new FileIOPermission(PermissionState.None); fiop.AllFiles = FileIOPermissionAccess.PathDiscovery; fiop.Assert(); try { assemblyLoc = typeof(Object).Assembly.Location; } finally { CodeAccessPermission.RevertAssert(); } string manifestLoc = null; string installDir = null; if (assemblyLoc != null) { installDir = Path.GetDirectoryName(assemblyLoc); const string manifestName = "XPThemes.manifest"; manifestLoc = Path.Combine(installDir, manifestName); } if (manifestLoc != null && installDir != null) { enableThemingActivationContext = new ACTCTX(); enableThemingActivationContext.cbSize = Marshal.SizeOf(typeof(ACTCTX)); enableThemingActivationContext.lpSource = manifestLoc; // Set the lpAssemblyDirectory to the install // directory to prevent Win32 Side by Side from // looking for comctl32 in the application // directory, which could cause a bogus dll to be // placed there and open a security hole. enableThemingActivationContext.lpAssemblyDirectory = installDir; enableThemingActivationContext.dwFlags = ACTCTX_FLAG_ASSEMBLY_DIRECTORY_VALID; // Note this will fail gracefully if file specified // by manifestLoc doesn't exist. hActCtx = CreateActCtx(ref enableThemingActivationContext); contextCreationSucceeded = (hActCtx != new IntPtr(-1)); } } // If we return false, we'll try again on the next call into // EnsureActivateContextCreated(), which is fine. return contextCreationSucceeded; } } // All the pinvoke goo... [DllImport("Kernel32.dll")] private extern static IntPtr CreateActCtx(ref ACTCTX actctx); [DllImport("Kernel32.dll")] private extern static bool ActivateActCtx(IntPtr hActCtx, out UIntPtr lpCookie); [DllImport("Kernel32.dll")] private extern static bool DeactivateActCtx(uint dwFlags, UIntPtr lpCookie); private const int ACTCTX_FLAG_ASSEMBLY_DIRECTORY_VALID = 0x004; private struct ACTCTX { public int cbSize; public uint dwFlags; public string lpSource; public ushort wProcessorArchitecture; public ushort wLangId; public string lpAssemblyDirectory; public string lpResourceName; public string lpApplicationName; } } }
+9
source share

I recently ran into this problem when debugging code using TaskDialogDemo in CodePack. This is how I fixed it. The problem with this is that if I open two or three dialogs, it throws a SEHException, which I did not understand how to fix. So beware of the buyer.

Add Core \ Interop \ TaskDialogs \ EnableThemingInScope.cs :

 using System; using System.IO; using System.Runtime.InteropServices; using System.Security; using System.Security.Permissions; using System.Windows.Forms; namespace Microsoft.WindowsAPICodePack.Dialogs { /// http://support.microsoft.com/kb/830033 /// <devdoc> /// This class is intended to use with the C# 'using' statement in /// to activate an activation context for turning on visual theming at /// the beginning of a scope, and have it automatically deactivated /// when the scope is exited. /// </devdoc> [SuppressUnmanagedCodeSecurity] internal class EnableThemingInScope : IDisposable { // Private data private uint cookie; private static ACTCTX enableThemingActivationContext; [System.Diagnostics.CodeAnalysis.SuppressMessage( "Microsoft.Reliability", "CA2006:UseSafeHandleToEncapsulateNativeResources" )] private static IntPtr hActCtx; private static bool contextCreationSucceeded = false; public EnableThemingInScope( bool enable ) { cookie = 0; if ( enable && OSFeature.Feature.IsPresent( OSFeature.Themes ) ) { if ( EnsureActivateContextCreated() ) { if ( !ActivateActCtx( hActCtx, out cookie ) ) { // Be sure cookie always zero if activation failed cookie = 0; } } } } ~EnableThemingInScope() { Dispose(); } void IDisposable.Dispose() { Dispose(); GC.SuppressFinalize( this ); } private void Dispose() { if ( cookie != 0 ) { try { if ( DeactivateActCtx( 0, cookie ) ) { // deactivation succeeded... cookie = 0; } } catch ( SEHException ) { // Robpol86: I don't know how to fix this! } } } [System.Diagnostics.CodeAnalysis.SuppressMessage( "Microsoft.Reliability", "CA2002:DoNotLockOnObjectsWithWeakIdentity" )] private static bool EnsureActivateContextCreated() { lock ( typeof( EnableThemingInScope ) ) { if ( !contextCreationSucceeded ) { // Pull manifest from the .NET Framework install // directory string assemblyLoc = null; FileIOPermission fiop = new FileIOPermission( PermissionState.None ); fiop.AllFiles = FileIOPermissionAccess.PathDiscovery; fiop.Assert(); try { assemblyLoc = typeof( Object ).Assembly.Location; } finally { CodeAccessPermission.RevertAssert(); } string manifestLoc = null; string installDir = null; if ( assemblyLoc != null ) { installDir = Path.GetDirectoryName( assemblyLoc ); const string manifestName = "XPThemes.manifest"; manifestLoc = Path.Combine( installDir, manifestName ); } if ( manifestLoc != null && installDir != null ) { enableThemingActivationContext = new ACTCTX(); enableThemingActivationContext.cbSize = Marshal.SizeOf( typeof( ACTCTX ) ); enableThemingActivationContext.lpSource = manifestLoc; // Set the lpAssemblyDirectory to the install // directory to prevent Win32 Side by Side from // looking for comctl32 in the application // directory, which could cause a bogus dll to be // placed there and open a security hole. enableThemingActivationContext.lpAssemblyDirectory = installDir; enableThemingActivationContext.dwFlags = ACTCTX_FLAG_ASSEMBLY_DIRECTORY_VALID; // Note this will fail gracefully if file specified // by manifestLoc doesn't exist. hActCtx = CreateActCtx( ref enableThemingActivationContext ); contextCreationSucceeded = (hActCtx != new IntPtr( -1 )); } } // If we return false, we'll try again on the next call into // EnsureActivateContextCreated(), which is fine. return contextCreationSucceeded; } } // All the pinvoke goo... [DllImport( "Kernel32.dll" )] private extern static IntPtr CreateActCtx( ref ACTCTX actctx ); [DllImport( "Kernel32.dll" )] private extern static bool ActivateActCtx( IntPtr hActCtx, out uint lpCookie ); [DllImport( "Kernel32.dll" )] private extern static bool DeactivateActCtx( uint dwFlags, uint lpCookie ); private const int ACTCTX_FLAG_ASSEMBLY_DIRECTORY_VALID = 0x004; private struct ACTCTX { public int cbSize; public uint dwFlags; public string lpSource; public ushort wProcessorArchitecture; public ushort wLangId; public string lpAssemblyDirectory; public string lpResourceName; public string lpApplicationName; } } }

Then in Core \ Interop \ TaskDialogs \ NativeTaskDialog.cs on line 93 (above HResult hresult = TaskDialogNativeMethods.TaskDialogIndirect) the section looks like this (in the end you will have three new lines)

 // Here is the way we use "vanilla" P/Invoke to call TaskDialogIndirect(). HResult hresult; using ( new EnableThemingInScope( true ) ) { hresult = TaskDialogNativeMethods.TaskDialogIndirect( nativeDialogConfig, out selectedButtonId, out selectedRadioButtonId, out checkBoxChecked ); }
+4
source share

I have the same problem with Visual Studio in debug mode. So far I have not found a workaround, it works fine in Release mode.

+1
source share

This page describes how to add a custom manifest to your project to tell Windows to download the new comctl32.dll file (version 6.0):

Does your manifest have the correct dependency on comctl32.dll? Have you embedded the generated manifest?

0
source share

More articles:


All Articles