Marshaling is an important part of .NET interop. It allows you to call into unmanaged code from managed code. This column will help you get started.
Yi Zhang and Xiaoying Guo
MSDN Magazine January 2008
View Complete Post
There are many factors to consider when building your app with both managed and native code. Find out how to employ interop and how to choose the interop that's right for you.
MSDN Magazine January 2009
There are plenty of times when you need to get information on running processes, not the least of which is during performance tuning. Using the techniques in this article and special .NET classes you'll see how to get a process' ID, name, priority, number of threads, kernel handle, and memory consumption, as well as its user-mode, kernel-mode, and total elapsed running time and put them to use in a custom app called AssemblyBrowser.
MSDN Magazine October 2004
when we compile our vb.net or c#.net code (say in a simple console application) then in bin\Debug folder a .exe file is created.Is that a managed code? when i directly execute this file,will this target CLR ? or will it directly run on OS ?
Why there is ConsoleApplication1.vshost.exe.manifest files created in that folder ?
What is .pdb file ?
That executable file is also created in obj\Debug folder .Why ?
This article will share some of the best practices that the Base Class Libraries (BCL) team devised as they added the code contract libraries and started to take advantage of them in their own code.
MSDN Magazine August 2009
This article discusses the Project Linker tool and other techniques to create applications that target both WPF and Silverlight from a single code base.
Erwin van der Valk
Here's a look at how code fails and techniques for writing more reliable and resilient managed code.
Alessandro Catorcini and Brian Grunkemeyer
MSDN Magazine December 2007
While multi-core processors have become increasingly common, most applications still fail to take advantage of multiple cores. Here's an overview of creating multithreaded applications that benefit from these new processors.
Daan Leijen and Judd Hall
MSDN Magazine October 2007
When is the .NET Garbage Collector unable to reclaim memory? The answer might surprise you. Stay tuned.
MSDN Magazine January 2007
Smart cards are a compelling alternative to the reliance on passwords, which are the weakest link in authentication systems. Get the Windows smart card programming basics here.
MSDN Magazine November 2006
Many of you are no doubt in the process of upgrading to Visual StudioÃÂ® 2005, so I thought now would be a good time to relate some of my own experiences with the new compiler. What took me so long? Hey, I'm a retro kind of guy! Better late than never!.
MSDN Magazine June 2006
In today's security-conscious environments, a reliable audit trail is a valuable forensic tool The Windows Server 2003 operating system provides features that let you enable a wide range of applications to make use of auditing functionality. This article looks at auditing from the operating system perspective and describes a sample managed code implementation that will allow you to add auditing to your own server applications.
MSDN Magazine October 2005
When the author was faced with implementing support for changing a security descriptor on an object, he noticed there was not support for that operation in .NET. So he devised two solutions to the problem: the first, simpler one, is tailored to the .NET Framework 1.1 and can be used today. The second solution incorporates several advanced features available only in the .NET Framework 2.0. Both are presented here.
MSDN Magazine March 2005
While you may well be excited about the prospect of building managed smart tags, there is little information available to help you create them using .NET. In this article the author fills in the blanks. Along the way he discusses the Microsoft Office Smart Tag List XML schema, advanced managed smart tags for Office 2003 and Office XP, and deploying these features in an organization.
MSDN Magazine February 2005
Managed applications rely on the garbage collector in the .NET Framework to allocate and clean up memory. The little CPU time spent performing garbage collection (GC) is usually a fair trade-off for not having to worry about memory management. But for applications in which CPU time and memory are precious resources, minimizing the time spent garbage collecting can greatly improve application performance and robustness. Find out how to manage memory all over again.
MSDN Magazine January 2005
MSDN Magazine July 2004