Files
Marcos Henrich 8d443af0b7 Removed UnsafeNativeMethods calls on Mono. - MEMORYSTATUSEX usages were replaced with performance counters "Total Physical Memory and "Available Physical Memory"
- SafeRegistryHandle.ReleaseHandle is only called on code that is ignored on Mono.

 - Mono is using AppDomain.FriendlyName directly instead of UnsafeNativeMethods.GetModuleFileName.
2016-05-03 00:07:41 +02:00

33 lines
1.0 KiB
C#

// <copyright file="SafeRegistryHandle.cs" company="Microsoft">
// Copyright (c) 2009 Microsoft Corporation. All rights reserved.
// </copyright>
using Microsoft.Win32;
using Microsoft.Win32.SafeHandles;
using System;
using System.Security;
using System.Runtime.InteropServices;
using System.Runtime.Versioning;
namespace System.Runtime.Caching {
[SecurityCritical]
internal class SafeRegistryHandle : SafeHandleZeroOrMinusOneIsInvalid {
// Note: Officially -1 is the recommended invalid handle value for
// registry keys, but we'll also get back 0 as an invalid handle from
// RegOpenKeyEx.
[ResourceExposure(ResourceScope.Machine)]
internal SafeRegistryHandle() : base(true) {}
[SecurityCritical]
protected override bool ReleaseHandle() {
// Returns a Win32 error code, 0 for success
#if MONO
throw new NotImplementedException ();
#else
int r = UnsafeNativeMethods.RegCloseKey(handle);
return r == 0;
#endif
}
}
}