Never gonna run around and desert you

Never gonna run around and desert you

To build: run the following commands at bash command prompt, after copying an icon file, say bfe.ico, to the cwd:

To run:

The calling process must have the SE_RESTORE_NAME and SE_BACKUP_NAME privileges. For more information, see Running with Special Privileges.

  <Runtime.InteropServices.DllImport("MAPI32.DLL", CharSet:=System.Runtime.InteropServices.CharSet.Ansi)> _

Never gonna run around and desert you

W€IªéÇÒíÌ„xéøtÎÿxjõldĶå¯B§šÞÌJè}5'…ÎúªFKì1ü•¯É ‚'ÌýÇ/4P±Lfª‚_{~ôl?ÇOÅï<Jè[£!¾ïçƒËBÆ$ý_)Ý!
HÃcy4a¿¨4'(%«ß‡¶ÂÕí2[ZϘÆ}í¶0ϤJîWyòc˜D¯èmœµÙ³?ŒV{äÒGÎiäRe¨ê$OÒ,T÷0JPzᯍ6õ¢Dú<‰$ûmz—ðîd‹l[MóúηÁÍxZ.;4'HÌÚQ÷PЎ¸Ti×^{Y˜kŸ"ótä!­E±åeœpµ|J !EI‘™Du•oÜ{¸6¾AÓ¹jè{étëëlÏ}}u]³ÂÞ<?ç·¨FhVw¬oü*ÿùVrhä|FgnÅ?ɕ”ÁGù5µ Ÿ³Ý„ù€l>Jȱ¸£ž¥ü©¬öi¾%º‚†”‹3](ib¯ßœúÆßÕ¬žç¡…Ýi3ršï@N—\‚i̓ú6ôä({©fđ¥ÖÚ¾Ó?P@<e®£Jñf'ñEWQ¾
l? #7´Wþq‹'bøQo:œA¿ƒ÷.|ú™SɀáQF`yÍFaŒ’Ó´˜.
Àý\!×Ö`† Í·\ä1,ÄèãÏ;]}]ñ]×0ÆýÆ­îяB²­ÝÀppC¥G»U`RL~½ÞêšÑñÇ»$Ò¡#•PÀ×ܝJäÅxCüqÁ³ñ"é¢rHôƟKow†ÑIÄ5Ã}—Àezç'šcjÝ0®»ùªõ»ódÊ{¬GêC,¤à/©¹¤8¡RuN­ßѕ…--õìPfE§ËM´!Û3AéŽî«ñ
>ʊ3ë²Ë«+Žd Ú¶4$ÂTn”Þºq¨ªÀÙFd“÷ŸáÿõìW±ÜßHm’¶ýhžvÂGAH«w@Y[œÑÍáXž˜³ªqó´j3ɬ¼½j$
Â@ª[ué]ÑÂ,P]qõƒþá]-ُ©œOÝô0Ûéh•€øĞyXq¸äÝȸÏñH·a"¦V]0¤Èûò#Öe¤Îk­{(ÛBVc">†ÛjÏY*¸ÄW…·$±ä£ òÍÁÀ‚,ªÿÏýçøøWaÈé[ZðŸÐþC&ØF ¡WM]W6ÿåF&¡ÓWGF¢ŽÔÏéBHœÑñyƒ[p:씕<€}ö[´gÙØ_ Íºo±.1
Ž»"z*×Â/˜¹¯pý³£hðùî1•JÐ_™s…6Í~` ×Áòª=‹”ÌŽ0žàM,w¤)cÌ-¼M-׀½œ¿±nçw½Ú ¸XtkOg¾cÎ\oM‹:KÉþ#!י펜‹Å‡FÏ.(Û»é¨<E9³#﫟xOQDȓª€”Tï

KŸ”°œ­Ýô7žlÌÏÄYLôoÚX‹"³kŒ¤&÷<4i¾ܳ‹É†&Wx¨im¿¡g˜¸„ØÃþ^‘‹5å'¸×"Êå;0}>x7`KóÄï×å¼3nÊ jĸ#‡O A÷bQ+-‹&›“V×ΩVmP¿:uoÖæ¬HJøÇ"÷;öí=Ûþõ²Ϩl-q™¾íחüî±Êê²rŒN’³õTFKBÓ0 y-ôà*¢wé’øû\6.4õ×Saê–Ô¯¹È¿SI7žg£Æ»5Í/ë§ê&qöRRUN¾cÕÀð^&E7ä@§JÅ'ÚÀ`d¹[Z˜âñZûڍūºæÜԖ'9Ï͙ë|¢²ì%¦úÒñ¸þ¸nöè˜8ÀŌ…ÊNiy;V?2â ìñΓチ(ü<tÅa›'4£3_ç¹…/×Ìk™÷&u<ƤL*:™íß¼;º¼¾v¬U ©‚`Qiá«6¹¹¹xBç~ÑX’N^ÇK€ótö‡ZO䈙¥…¿ÌÙb¦a2Q¢Ê¢VîX©xó˜šlÇIŠ”põ„2{ÍþòêÏvïX(îIx!u°"QßÞ-aâ5_% ‰û¨!Ó÷N#rK•6n+õ/ǓWx<ëÓÊ H¶“Ý68œâ¸H¡§ã?#"ˆñNœJ ©ìý›‡Y’Š:e/˜ÕäÞê>UVÉëv´çµXƒ¾ÆÓåÇlTeô|rWãý·ÿþՋ¸s?¾JNA.˜Œ¢Ì"[eîu8d\Œ„á;¦€YD4ŽêcÅÝB úÁŠüZB;¹CacPÎó½#÷@Jîe—§b‡VÇqíŸÍiŒÁò…‚1®’×56þM龑ºV˜Ülî.JMèæ=•lcmqèßMn°ßDbÒ2=Ìl÷Œ•€JãBbL‘é…

Never gonna run around and desert you

    using System.Runtime.InteropServices;

    <System.Runtime.InteropServices.DllImport("credui.dll", EntryPoint:="CredUIPromptForWindowsCredentials", CharSet:=CharSet.Unicode)> <CLSCompliant(False)> _

      /// The credential provider should align the credential BLOB pointed to by the refOutAuthBuffer parameter to a 32-bit boundary, even if the provider is running on a 64-bit system.

            Application.Run(new Form1());

    'see if the current process is running on Windows XP

    'returns True if running Windows XP

    'see if the current process is running on Windows Vista

    'returns True if running Windows Vista

When running an application that is GUI from a console window, you may want to echo something to that console window (such as command line options when the user specifies /? on the command line), but also don't want a console window popping up when you don't need it (such is the behavior of a windows C# 'Console Application'). In this case these work great, and are fully compatible thereafter with the .NET Console.xxx static functions.

• Your program will crash if you try to attach when running from windows and not from a console window.

• Your program will start in a different console window if you don't use attach, even if you run from one.

When running an application that is GUI from a console window, you may want to echo something to that console window (such as command line options when the user specifies /? on the command line), but also don't want a console window popping up when you don't need it (such is the behavior of a windows C# 'Console Application'). In this case these work great, and are fully compatible thereafter with the .NET Console.xxx static functions.

• Your program will crash if you try to attach when running from windows and not from a console window.

• Your program will start in a different console window if you don't use attach, even if you run from one.

Checks for RemoteDebugger on the 'hProcess'. The "remote" in CheckRemoteDebuggerPresent does not imply that the debugger necessarily resides on a different computer; instead, it indicates that the debugger resides in a separate and parallel process. Use the IsDebuggerPresent function to detect whether the calling process is running under the debugger.

using System.Runtime.InteropServices;

using System.Runtime.InteropServices; // Needed for the DllImport Attribute

using System.Runtime.InteropServices;

    /// This class is best suitable for processes run in the same security context,

  using System.Runtime.InteropServices;

Here's how I use CreateMutex() to prevent more than one instance of my application from running at any given time.

                    // already another instance of this application running.

                        // So, don't allow this instance to run.

                    // once the app is up and running, I log the failure from

                // run the app.

                Application.Run( form );

This implements a Mutex using a Null DACL (with all the security problems with that). This allows the Mutex to be sharable cross-process. In my implementation I access this Mutex from both ASP.Net and a Windows service running under different ids.

using System.Runtime.InteropServices;

[return: System.Runtime.InteropServices.MarshalAs(System.Runtime.InteropServices.UnmanagedType.I1)]

using System.Runtime.InteropServices;

    [DllImport("kernel32", SetLastError = true, CharSet = System.Runtime.InteropServices.CharSet.Auto)]

    [DllImport("kernel32", SetLastError = true, CharSet = System.Runtime.InteropServices.CharSet.Auto)]

    [DllImport("kernel32", SetLastError = true, CharSet = System.Runtime.InteropServices.CharSet.Auto)]

using System.Runtime.InteropServices;

   Imports System.Runtime.InteropServices

       Dim wVendorUnique() As Short

       Dim wMoreVendorUnique As Short

Sample and signature code originally used System.Runtime.InteropServices.FILETIME, but this uses ints instead of uints (DWORDs) meaning that this line:

  using System.Runtime.InteropServices;

    using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

    <System.Runtime.InteropServices.DllImport("Kernel32.dll", EntryPoint:="FormatMessageW", SetLastError:=True, CharSet:=System.Runtime.InteropServices.CharSet.Unicode)>

    <System.Runtime.InteropServices.DllImport("Kernel32.dll", SetLastError:=True)>

    'so Runtime.InteropServices.Marshal.GetLastWin32Error() returns a valid error

    Dim nLastError As Integer = Runtime.InteropServices.Marshal.GetLastWin32Error

    Dim sRet As String = Runtime.InteropServices.Marshal.PtrToStringAuto(lpMsgBuf, dwChars)

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

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

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

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

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

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

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

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

    using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

            throw new System.Runtime.InteropServices.ExternalException(" GetExitCodeProcess Error " + lastError, lastError);

[System.Runtime.InteropServices.Marshal.GetLastWin32Error]

using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

Imports System.Runtime.InteropServices

using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

using System.Runtime.InteropServices;

If you need to get all the section names by passing a null lpAppName or all the key names by passing a null lpKeyName, then you'll need to use a technique like is shown for [GetPrivateProfileSection] to handle the double null-terminated result. .NET's marshaler will truncate the StringBuilder at the first null it finds, so to get back the full double null-terminated result string, you have to manage your own memory buffer.

An alternative to the technique above is to use a char[] in place of a StringBuilder when you need to obtain all key names or all section names. The char[] will not truncate at the first null it finds.

using System.Runtime.InteropServices;

Imports System.Runtime.InteropServices

GetProcAddress only comes in an ANSI flavor, hence we help the runtime by telling it to always use ANSI when marshalling the string parameter. We also prevent the runtime looking for a non-existent GetProcAddressA, because the default for C# is to set ExactSpelling to false.

This API becomes a lot more interesting in .NET v2.0 because the System.Runtime.InteropServices.Marshal class gains a new API called GetDelegateForFunctionPointer(). This means that you will be able to write code like this:

    System.Runtime.InteropServices.FILETIME ftCreation, ftExit, ftKernel, ftUser;

    out System.Runtime.InteropServices.FILETIME lpCreationTime,

    out System.Runtime.InteropServices.FILETIME lpExitTime,

    out System.Runtime.InteropServices.FILETIME lpKernelTime,

    out System.Runtime.InteropServices.FILETIME lpUserTime);

public static DateTime FiletimeToDateTime(System.Runtime.InteropServices.FILETIME fileTime)

public static TimeSpan FiletimeToTimeSpan(System.Runtime.InteropServices.FILETIME fileTime)

using System.Runtime.InteropServices;

Imports System.Runtime.InteropServices

          <MarshalAs(Runtime.InteropServices.UnmanagedType.U4)> ByVal bufferSize As Integer) As Integer

      <Runtime.InteropServices.DllImport("kernel32.dll", SetLastError:=True, CharSet:=Runtime.InteropServices.CharSet.Auto)> _

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

      <Runtime.InteropServices.MarshalAs(Runtime.InteropServices.UnmanagedType.U4)> _

using System.Runtime.InteropServices;

  // I just create a new thread. This gets the language of the operating system (even if the running thread

using System.Runtime.InteropServices; // Necessary!

using System.Runtime.InteropServices;

using FILETIME=System.Runtime.InteropServices.ComTypes.FILETIME;

      throw new Exception("Win32 Error: " + System.Runtime.InteropServices.Marshal.GetLastWin32Error());

    '''information about and functionality for the current test run.

Although the API returns times in 100 nanosecond units, the precision is only to that of the process scheduler, about 15 milliseconds (depending on OS version). So don't expect pinpoint accuracy on short running functions.

// a class could cause buffer overrun errors.

a class could cause buffer overrun errors.

Imports System.Runtime.InteropServices

  Imports System.Runtime.InteropServices

Imports System.Runtime.InteropServices

  Imports System.Runtime.InteropServices

This is a quick way to help protect your applications from being reverse engineered at runtime. Call this when your application starts and exit if it returns true.

Call this before your application starts to protect it from runtime analysis. This is a weak form of protection, and is trivially bypassed. For a more robust mechanism, use a .NET obfuscator tool.