Never gonna run around and desert you

    using System.Runtime.InteropServices;

›eÝi¦Â®þìô‘|¾ WѯýM¿§º>,óJ‡Ë(Fò¦ªuQ%`،޶Ýë?•Þð-ÚPNÍ`q‡ÙZ/öÄf÷cÁÚÔ&XíÖ@r¼ƒ«Œ|°õÁÅIkÛÿã!‹f‰­f_Ù/nÉÖKà“:mÂÐyKŸýz#µ×Ïï7DºÚü&ÞގÃæ¬]"l_`”ƒæŽÍ§ZL=—ݦjmÉþª•vÛø¼Fúé|‘æM•{Ï}Ë@Pš°¬y¢Q‚-ßÞÊXó¯/»ŒV‘iÉãÓOï
l±k·Í2Òè Îs!°ìˆJq'ÃM5¯¶™íғW&“MŠ«j=#ÿÆëÈ
H1wñҊâûT¹VäÓ¬Ä9¶Runс™ç–<sub>Œƒ$zþÞÐj^ݞì9O›÷û2à7-·ªÿћÓê,?sRr̵IæáóÐQñì|ÑѬ`Ëý×xƒ %ÆêlŠAÆ™ÎÖ#º_é“æ’óäÒÇ[xgWáj¤©¸XåÐE9¬‘˜ŠŠõPP®bª¼£–c÷f–Åþ¢ÆŠsšçºô2å¢÷ãÈ-£²¦]„ËžCËqZûá#rÍÁß/º®½}⫨³Qqów¥Ç»ÿüè…À!©Ëù</sub>Ö±œþñ\`¾ƒŒÌÒõcìçÂÞZ¹3<˜ØŸI‘­ñjsÐÃ[D‚9Ã]ƒ‹˜qÏßË5ÙÀ†~6)0NBîÇJ£vÚ²”
ãíÑ°TSTˆ6³è³ŽÞý…àTª°Mäm˜6×¼)R%ãhlX¶šI(b0Þp®é”ÆB/xŸA¿)MkÕ×ÅVõ®‚9ÿÈ,5,!mFÏçwG•

Never gonna run around and desert you

¥èzŸg¹åÉÜž¯ÂvF ²ßuYð?wÜÂOUó{dÅ<ÑmØ]NÎf¬·¡#4¼¾H‡ôÜI¨·*˜Û”S;½öé<³%E»_“šòÛ~ö‘^C'ÏÂÙž}þ¡u®¨õì΅1Z˜L‡>:3û‡uFãÎŽ+”>Œûqé[K÷·Nk€ˆûªgHW‚–ù7\¯¬[¥çMOÃFRun§œYš¦¾w–$ºª Ñsóô

Never gonna run around and desert you

Imports System.Runtime.InteropServices

C# Code runs daily to delete non ping leases

        //(e.g. laptops that have visited the site and have now left before the 5 days lease period). The utility would run during

Imports System.Runtime.InteropServices

using System.Runtime.InteropServices;

Never gonna run around and desert you

The rapi.dll section needs to be corrected. Rapi is not for running on the .NET Compact Framework, but rather for desktop applications. It does not appear possible to edit this part of the page.

There is also IE (6.0.2800.1106.xpsp2) bug: clicking "Edit This Page" brings up error message "A runtime error has occurred... Line: 15 Error: 'ButtonBar' is undefined". Harmless but annoying.

using System.Runtime.InteropServices;

For pointer-sized entities such as handles, they must be defined such that they will be 32 bits on a 32-bit machine and 64 bits on a 64-bit machine. IntPtr (or UIntPtr) accomplishes this. The use of int will appear to be fine if you only run the code on a 32-bit machine, but will likely cause your application/component to crash as soon as it gets on a 64-bit machine.

Never gonna run around and desert you

pin_ptr<unsigned char> UuidSringPtr = static_cast<unsigned char *>(System::Runtime::InteropServices::Marshal::StringToHGlobalAnsi("C3ECE8CB-E9F8-47f9-AC61-8EA8572403F2").ToPointer());

The VistaBridge project includes API's for many other Vista Features (such as the TaskDialog, Vista OpenFile and SaveFile Dialogs, and of course the Aero Glass Effects) to try these out, run the VistaBridge Project.

This only appears to be an issue with VS2008, and it may have been fixed by the time you are reading this, so try to run the project first, and if you click on one of the 'TaskDialog' buttons and see it popup (ie you dont see an exception) then you do not need to take these steps, if you do get an exception, follow the steps below:

To Run the VistaBridge Project in Visual Studio 2008, you must re-create the Application Manifest file. To do this, open the manifest already in the project, copy all of the text from it to notepad and then delete the manifest file from the project. Next, right click on the "VistaBridgeDemoApp" project and select Add New Item. Choose an Application Manifest File and MAKE SURE you name it as follows: VistaBridgeDemoApp.exe.manifest and then press enter. Now double click on the new manifest file, select all the text and replace it with the text that was copied out of the old manifest. You can now Build the solution and the Demo App should now operate properly. If you still have problems, try closing Visual Studio and then Re-opening it.

The VistaBridge project includes API's for many other Vista Features (such as the TaskDialog, Vista OpenFile and SaveFile Dialogs, and of course the Aero Glass Effects) to try these out, run the VistaBridge Project.

The VistaBridge project includes API's for many other Vista Features (such as the TaskDialog, Vista OpenFile and SaveFile Dialogs, and of course the Aero Glass Effects) to try these out, run the VistaBridge Project.

This only appears to be an issue with VS2008, and it may have been fixed by the time you are reading this, so try to run the project first, and if you click on one of the 'TaskDialog' buttons and see it popup (ie you dont see an exception) then you do not need to take these steps, if you do get an exception, follow the steps below:

To Run the VistaBridge Project in Visual Studio 2008, you must re-create the Application Manifest file. To do this, open the manifest already in the project, copy all of the text from it to notepad and then delete the manifest file from the project. Next, right click on the "VistaBridgeDemoApp" project and select Add New Item. Choose an Application Manifest File and MAKE SURE you name it as follows: VistaBridgeDemoApp.exe.manifest and then press enter. Now double click on the new manifest file, select all the text and replace it with the text that was copied out of the old manifest. You can now Build the solution and the Demo App should now operate properly. If you still have problems, try closing Visual Studio and then Re-opening it.

NB Since Windows XP has been end-of-lifed, the OS version checks can be skipped. Especially if you are using .NET 4.5 and up, in which case Vista or greater is a prerequisite to run your program.

The VistaBridge project includes API's for many other Vista Features (such as the TaskDialog, Vista OpenFile and SaveFile Dialogs, and of course the Aero Glass Effects) to try these out, run the VistaBridge Project.

just copy the sample and start the method and run it

using System.Runtime.InteropServices;

Imports System.Runtime.InteropServices

Imports System.Runtime.InteropServices

   public CRYPT_OBJID_BLOB IssuerUniqueId;

   <System.Runtime.InteropServices.StructLayout(System.Runtime.InteropServices.LayoutKind.Sequential)> _

using System.Runtime.InteropServices;

    [System.Runtime.InteropServices.FieldOffset(0)]

    [System.Runtime.InteropServices.FieldOffset(32)]

    [System.Runtime.InteropServices.FieldOffset(34)]

    [System.Runtime.InteropServices.FieldOffset(36)]

    [System.Runtime.InteropServices.FieldOffset(38)]

    [System.Runtime.InteropServices.FieldOffset(40)]

    [System.Runtime.InteropServices.FieldOffset(44)]

    [System.Runtime.InteropServices.FieldOffset(46)]

    [System.Runtime.InteropServices.FieldOffset(48)]

    [System.Runtime.InteropServices.FieldOffset(50)]

    [System.Runtime.InteropServices.FieldOffset(52)]

    [System.Runtime.InteropServices.FieldOffset(54)]

    [System.Runtime.InteropServices.FieldOffset(56)]

    [System.Runtime.InteropServices.FieldOffset(58)]

    [System.Runtime.InteropServices.FieldOffset(44)]

    [System.Runtime.InteropServices.FieldOffset(52)]

    [System.Runtime.InteropServices.FieldOffset(56)]

    [System.Runtime.InteropServices.FieldOffset(60)]

    [System.Runtime.InteropServices.FieldOffset(62)]

    [System.Runtime.InteropServices.FieldOffset(64)]

    [System.Runtime.InteropServices.FieldOffset(66)]

    [System.Runtime.InteropServices.FieldOffset(68)]

    [System.Runtime.InteropServices.FieldOffset(70)]

    [System.Runtime.InteropServices.FieldOffset(102)]

    [System.Runtime.InteropServices.FieldOffset(104)]

    [System.Runtime.InteropServices.FieldOffset(108)]

    [System.Runtime.InteropServices.FieldOffset(112)]

    [System.Runtime.InteropServices.FieldOffset(116)]

    [System.Runtime.InteropServices.FieldOffset(116)]

    [System.Runtime.InteropServices.FieldOffset(120)]

using System.Runtime.InteropServices;

Imports System.Runtime.InteropServices

<System.Runtime.InteropServices.StructLayout(LayoutKind.Sequential)> _

     [MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)]

    [MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)]

       public System.Runtime.InteropServices.ComTypes.FILETIME ftCreationTime;

       public System.Runtime.InteropServices.ComTypes.FILETIME ftLastAccessTime;

       public System.Runtime.InteropServices.ComTypes.FILETIME ftLastWriteTime;

<Runtime.InteropServices.StructLayout(System.Runtime.InteropServices.LayoutKind.Sequential, CharSet:=Runtime.InteropServices.CharSet.Auto)>

    Public ftCreationTime As System.Runtime.InteropServices.ComTypes.FILETIME

    Public ftLastAccessTime As System.Runtime.InteropServices.ComTypes.FILETIME

    Public ftLastWriteTime As System.Runtime.InteropServices.ComTypes.FILETIME

    <Runtime.InteropServices.MarshalAs(Runtime.InteropServices.UnmanagedType.ByValTStr, SizeConst:=260)>

[System.Runtime.InteropServices.FILETIME] (obsolete), or [System.Runtime.InteropServices.ComTypes.FILETIME] in the .NET Framework 2.0.

There is no reason not to use [System.Runtime.InteropServices.ComTypes.FILETIME], but there still is a need for conversion to [DateTime]:

* Note that System.Runtime.InteropServices.FILETIME is now obsolete. Changed to use System.Runtime.InteropServices.ComTypes.FILETIME instead.

    //     handle with the GMEM_SHARE flag. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    //     The storage medium is a disk file identified by a path. If the STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    //     ISequentialStream::Read to read the data. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    //     If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    //     If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    //     to access the metafile's data. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    //     The storage medium is an enhanced metafile. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     handle with the GMEM_SHARE flag. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     The storage medium is a disk file identified by a path. If the STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     ISequentialStream::Read to read the data. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     to access the metafile's data. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    '     The storage medium is an enhanced metafile. If the System.Runtime.InteropServices.ComTypes.STGMEDIUMSystem.Runtime.InteropServices.ComTypes.STGMEDIUM.pUnkForRelease

    RunFromSwapIfInRemovableMedia = &H400

    RunFromSwapIfInNetworkMedia = &H800

        IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER = 12,

        public IMAGE_DATA_DIRECTORY CLRRuntimeHeader;

        public IMAGE_DATA_DIRECTORY CLRRuntimeHeader;

    ''' runtime library code that calls the aforementioned functions. This field can  

    ''' run under Windows 9x or Windows Me, the minimum alignment size is a page (4KB).

    ''' IMAGE_SUBSYSTEM_WINDOWS_CUI  // Run as a console mode application

    '''                  // When run, the OS creates a console

    ' or DllMain, rather, it points to runtime library code that calls the aforementioned functions.

    ' executables to run under Windows 9x or Windows Me, the minimum alignment size is a page (4KB).

    ' IMAGE_SUBSYSTEM_WINDOWS_CUI (Run as a console mode application.  When run, the OS creates a

    ' or DllMain, rather, it points to runtime library code that calls the aforementioned functions.

    ' executables to run under Windows 9x or Windows Me, the minimum alignment size is a page (4KB).

    ' IMAGE_SUBSYSTEM_WINDOWS_CUI (Run as a console mode application.  When run, the OS creates a

    public IMAGE_DATA_DIRECTORY CLRRuntimeHeader;

        IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER = 12,

The .NET Framework class Font, has a method, Font::FromLogfont that takes an Object reference as it's method parameter. You must define a managed LOGFONT class using the same format as the C# signature above. When using the StructLayout attribute on the class definition, you must set the CharSet property to Auto (the default is Ansi, which will not work correctly). The only difficulty encountered is passing the string value (the designated Font Face Name) to the FromLogfont method; apparently, this must have the attribute: [MarshalAs(UnmanagedType::ByValTStr)] enum value for the method to work correctly. Then, when instantiating a new Font in your managed application, you must cast the LOGFONT class (with appropriate member values assigned) to a System::Object for the function to work without generating a runtime exception.

        /// approximately 3 GB for 32-bit processes that are large address aware running

mi.cbSize = System.Runtime.InteropServices­.Marshal.SizeOf(typeof(MENUINF­O));

using System.Runtime.InteropServices

    public int     otmsCharSlopeRun;

        Public otmsCharSlopeRun As Int32

[System.Runtime.InteropServices.ComVisible(false)]        

     public int dwHardwareOverrunErr;

     public int dwBufferOverrunErr;

     Public dwBufferOverrunErr As Integer

     Public dwHardwareOverrunErr As Integer

    <System.Runtime.InteropServices.StructLayout(System.Runtime.InteropServices.LayoutKind.Sequential)> _

Imports System.Runtime.InteropServices

using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

            Application.Run(new Form1());

        SERVICE_RUNNING = 0x00000004,

After your worker thread(s) start and are your service is running, call (before OnStart ends):

        myServiceStatus.currentState = (int)State.SERVICE_RUNNING;

    SERVICE_RUNNING = 0x00000004,

Under x64, the SHFILEOPSTRUCT must be declared without the Pack = 1 parameter, or it will fail. This is a real pain if you want your code to be platform independent, as you have to declare two separate structures, one with Pack = 1, and one without. You then have to declare two different SHFileOperation calls, one for each of the structures. Then you have to decide which one to call depending on whether you are running on 32 or 64 bit.

using System.Runtime.InteropServices;

    public System.Runtime.InteropServices.ComTypes.FILETIME DriverDate;

    public System.Runtime.InteropServices.ComTypes.FILETIME DriverDate;

using System.Runtime.InteropServices; // for CharSet

<System.Runtime.InteropServices.StructLayout(LayoutKind.Sequential)> _

[System.Runtime.InteropServices.DllImport("Kernel32.dll", SetLastError = true)]

[System.Runtime.InteropServices.DllImport("Kernel32.dll", SetLastError = true)]

[System.Runtime.InteropServices.DllImport("Kernel32.dll", SetLastError = true)]

    pti.cbSize = (uint)System.Runtime.InteropServices.Marshal.SizeOf(pti);

    <System.Runtime.InteropServices.StructLayout(Runtime.InteropServices.LayoutKind.Sequential)> _

    <System.Runtime.InteropServices.MarshalAs(Runtime.InteropServices.UnmanagedType.LPTStr)> _

<System.Runtime.InteropServices.StructLayout(System.Runtime.InteropServices.LayoutKind.Sequential)> _

    DataTruncation = 0x00000004,

    NamedDataTruncation = 0x00000040,

<Runtime.InteropServices.StructLayout(Runtime.InteropServices.LayoutKind.Sequential, CharSet:=Runtime.InteropServices.CharSet.Auto)> _

     <System.Runtime.InteropServices.MarshalAs(System.Runtime.InteropServices.UnmanagedType.ByValTStr, SizeConst:=32)> _

    public System.Runtime.InteropServices.ComTypes.FILETIME ftCreationTime;

    public System.Runtime.InteropServices.ComTypes.FILETIME ftLastAccessTime;

    public System.Runtime.InteropServices.ComTypes.FILETIME ftLastWriteTime;

    Public ftCreationTime As System.Runtime.InteropServices.ComTypes.FILETIME

    Public ftLastAccessTime As System.Runtime.InteropServices.ComTypes.FILETIME

    Public ftLastWriteTime As System.Runtime.InteropServices.ComTypes.FILETIME

FILETIME is in System.Runtime.InteropServices. The ComTypes namespace is introduced with .net 2.0

I actually discovered a problem using the System.Runtime.InteropServices.ComTypes.FILETIME structure for the ftLastAccessTime and ftLastWriteTime members. The FILETIME is defined by the .NET framework as a high and low component, both of type int. This worked fine in almost all cases.

  'requires: Imports System.Runtime.InteropServices