Programming Resources

A component model for the .NET CLR />http://www.google.ro/url?sa=t&source=web&cd=10&ved=0CGwQFjAJ&url=http%3A%2F%2Fsystems.ethz.pubzone.org%2Fservlet%2FAttachment%3FattachmentId%3D379%26versionId%3D1534932&rct=j&q=FindModuleByTypeRef&ei=YEyoTazIOM-Rswa-wfGPCA&usg=AFQjCNH5kelnN6xZg_V7RwizW3oVpuQVFg&cad=rja

How to: Request Permission to Access Unmanaged Code />http://msdn.microsoft.com/en-us/library/d0313z05.aspx

Code Access Security in the .NET Framework />http://www.devx.com/vb2themax/article/19886/1954 />http://www.reliablesoftware.com/articles/PreventingElevationofPrivilegeAttacks.html />http://www.wrox.com/WileyCDA/Section/Support-for-Security-in-the-Framework.id-107270.html

How to disable string Interning on CLR />http://social.msdn.microsoft.com/forums/en-US/clr/thread/c1c1d969-8d6b-4aaf-b7f4-3febedf3cd18/

The Complete Reference VB.NET />http://www.mediafire.com/?h5b4b4a959kxj5r

Inlining Java Native Calls at Runtime />http://www.slidefinder.net/I/Inlining_Java_Native_Calls_Runtime/5429232 />http://www.google.ro/#hl=ro&source=hp&biw=1024&bih=578&q=Inlining+Java+Native+Calls+at+Runtime&aq=f&aqi=&aql=&oq=&fp=aca76bf0002b48d8 />http://www.google.ro/url?sa=t&source=web&cd=3&ved=0CCcQFjAC&url=http%3A%2F%2Fwebdocs.cs.ualberta.ca%2F~amaral%2Fcascon%2FCDP05%2Fslides%2FCDP05-stepanian.pdf&rct=j&q=CDP05-stepanian&ei=J6N6Tby6EZD0sga_qKjcBw&usg=AFQjCNHimuDigrVUseiMQ0R5h-ivGATrSQ&cad=rja

Handling CoInitialize (and CoUninitialize!) />http://blogs.msdn.com/b/benkuhn/archive/2006/09/15/756401.aspx

Writing a JIT />http://www.sourcemod.net/devlog/?p=76

AsmJit AsmJit is complete x86/x64 JIT-Assembler for C++ language. It supports 32/64-bit x86 processors including all usable extensions (FPU, MMX, 3dNow, SSE, SSE2, SSE3 and SSE4) through type-safe API that mimics Intel assembler syntax and eliminates nearly all common mistakes that can be done by developers. AsmJit contains also high-level code generation classes that can be used as a portable way to create JIT code that should run on all supported architectures. High-level classes can handle various function calling-conventions, register allocation and 32/64-bit mode differences. AsmJit has been successfully tested by various C++ compilers (including MSVC, GCC and Borlan…

Turn MethodInfo to DynamicMethod />http://blogs.msdn.com/b/haibo_luo/archive/2006/11/07/turn-methodinfo-to-dynamicmethod.aspx />http://blogs.msdn.com/b/zelmalki/archive/2009/03/29/msil-injection-rewrite-a-non-dynamic-method-at-runtime.aspx />http://www.lesuna.com/blog/net-21453-23556-33073-22771-26426-26680-24515-31243-24207-20195-30721/

Application.Exit vs. Environment.Exit />http://geekswithblogs.net/mtreadwell/archive/2004/06/06/6123.aspx

Installing a global hot key with C# />http://www.liensberger.it/web/blog/?p=207 />http://stackoverflow.com/questions/3654787/global-hotkey-in-console-application

Logical Call Context: Flowing Data across Threads, AppDomains, and Processes />http://www.wintellect.com/cs/blogs/jeffreyr/default.aspx

.NET Memory Leak: XmlSerializing your way to a Memory Leak />http://blogs.msdn.com/b/tess/archive/2006/02/15/532804.aspx?PageIndex=3

The forty-first part of the C# Fundamentals tutorial examines the Stack class. This collection includes the functionality required in a 'Last In, First Out' (LIFO) stacking structure. Stacks allow items to be held for later extraction and processing. />http://www.blackwasp.co.uk/Stack.aspx Download: />http://cid-e8f82acbdb9dc8f4.office.live.com/self.aspx/.Public/Sample%20Code/StackDemo.zip

The first stage of Project Shellcode aims to become the knowledge base for all shellcode related resources, including white papers, tutorials, tools, links, assembly code, and of course shellcode. This will allow the community to submit their own shellcode and shellcode related resources to the project so that they are available for others to use and learn from, as well as allowing them to extend their own knowledge and skills by gaining access to new materials and previously unreleased shellcode. This also allows a bridge to be created that enables those new to shellcoding to use the resources at hand to advance their skills so that they too can contribute their…

Managed Windows API A collection of .NET components that wrap PInvoke calls to access native API by managed code />http://mwinapi.sourceforge.net/

CLR Injection: Runtime Method Replacer />http://www.codeproject.com/KB/dotnet/CLRMethodInjection.aspx

Have the Background Programs Lower Their Process Priority />http://www.novicksoftware.com/TipsAndTricks/Tips-Lower-your-Process-Priority-with-the-Win32-API.htm

The low-fragmentation heap (LFH) helps to reduce heap fragmentation. The LFH is not a separate heap. Instead, it is a policy that applications can enable for their heaps. When the LFH is enabled, the system allocates memory in certain predetermined sizes. When an application requests a memory allocation from a heap that has the LFH enabled, the system allocates the smallest block of memory that is large enough to contain the requested size. The system does not use the LFH for allocations larger than 16 KB, whether or not the LFH is enabled. // C# code: // Imports: [DllImport("kernel32.dll")] private static extern uint GetProcessHeaps(uint NumberOfHeaps, IntPtr[…

Change ImageBase of a PE File (Delphi) />http://sites.google.com/site/delphibasics/home/delphibasicssnippets/changeimagebaseofapefile

[VB.NET] JapaBrz's RunPe />http://www.l33thackers.com/showthread.php?tid=622

Quick Start Autoit files without any delay...and with any firewall />http://www.autoitscript.com/forum/topic/108296-mfc-quickrun-mem/

Using memory mapped files to conserve physical memory for large arrays: />http://www.codeproject.com/KB/recipes/MemoryMappedGenericArray.aspx

A Resource Monitor for NT 4.0 Compared to Windows 3.1, NT offers programmers many improvements over its 16-bit predecessor. For example, NT does away with many of the memory and resource limitations imposed by Windows 3.1. One particular Achilles’ heel for Windows 3.1 was the system-wide 64K memory limit for GDI objects, such as brushes and fonts. With such a low limit, it was relatively easy for Windows 3.1 to run out of space for GDI objects. NT 4.0 offers some improvement in this area, but there are still system-wide limits that you might find surprising. The same is true for USER objects, such as windows and menus. The bottom line is that efficient resource usage is s…