http://www.agiledeveloper.com/download.aspx. Here you’ll find articles and discussions related to .NET and software development by Venkat Subramaniam.
http://www.gotdotnet.com/team/clr/about_clr_performance.aspx. In addition to the CLR Profiler tool, at this URL you will find articles and discussions related to performance of managed code.
http://www.developer.com/open/article.php/989091. This is Jeffrey Richter’s article on how to properly implement the operations that all objects must exhibit. It talks about object equality, identity, hash codes, and cloning.
http://www.sourceforge.net/projects/ccnet. Cruise Control .NET is an open source automated continuous integration tool for Microsoft .NET. It uses tools such as NUnit and NAnt, and integrates with your source control system (e.g., CVS and Visual Source Safe) to automatically build and test your code as it is checked into the source control system.
http://blogs.msdn.com/csharpfaq. This is a site where you can ask and get answers to many C# Frequently Asked Questions.
http://msdn.microsoft.com/library/en-us/csspec/html/CSharpSpecStart.asp. This site contains the actual C# Language Specification.
http://msdn.microsoft.com/library/en-us/cpgenref/html/cpconNETFrameworkDesignGuidelines.asp.
This site presents design guidelines for developing class libraries and components using the .NET framework.
http://msdn.microsoft.com/archive/en-us/dnaraskdr/html/askgui06032003.asp. An article that discusses why locking the type metadata is a bad idea.
http://draconet.sourceforge.net. Like Cruise Control .NET, Draco.NET is an easy to use Windows service application for continuous integration.
http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-335.pdf. Common Language Infrastructure (CLI)--Partitions I to V (Standard ECMA-335 2nd). Here you will find definitions and details on CLI, CLS, and CTS.
http://blogs.msdn.com/csharpfaq/archive/2004/03/29/102224.aspx. Article titled “When should I use == and when should I use Equals?” discusses issues with the Equals()
method and the ==
operator.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/singletondespatt.asp. This article by Mark Townsend discusses the Singleton Design Pattern and its effective use in .NET.
http://www.gotdotnet.com/team/fxcop. FxCop is a code analysis tool that checks .NET code for conformance to the Microsoft .NET Framework Design Guidelines.
http://msdn.microsoft.com/msdnmag/issues/1100/GCI/default.aspx. Jeffrey Richter’s article titled “Garbage Collection: Automatic Memory Management in the Microsoft .NET Framework” presents in great detail the garbage collection heuristics in the .NET CLR.
http://groups.google.com. This is a great resource to search for just about any information you need. Most of the time you’ll find answers here to what you are looking for. At other times, you can take comfort that others are having similar pain.
http://www.gotdotnet.com. This .NET framework community web site has resources, articles, and discussions on various topics related to .NET.
http://www.interact-sw.co.uk/iangblog/2004/06/21/gethashcode. In this article, titled “The Rules for GetHashCode,” Ian Griffiths talks about the surprises of hash codes.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/cpconFinalizeDispose.asp. Here you’ll find Microsoft’s description of the Dispose Design Pattern.
http://www.yoda.arachsys.com/csharp/singleton.html. This interesting article delves deep into the issues with Singleton thread-safety.
http://www.gotdotnet.com/team/lang. This site has an up-to-date list of the available languages.
http://msdn.microsoft.com. Here you can search and access online documentation and articles related to Microsoft products in general.
http://msdn.microsoft.com/msdnmag. MSDN Magazine has a wealth of information. Here you will find several articles that are of interest to any .NET programmer.
http://sourceforge.net/projects/nant. NAnt is an open source Ant-like build tool for .NET. This tool helps you automate the build of your code and exercise your unit tests.
http://sourceforge.net/projects/ndoc. NDoc is a nice tool that allows you to generate HTML and MSDN like documentation. It uses reflection and XML comments in your code.
http://sourceforge.net/projects/nunit. NUnit is an open source unit testing tool for Microsoft .NET. Even though this originated from JUnit (Java unit testing tool), it has been written in C# and uses a number of .NET features. It can test your .NET application, regardless of the .NET language used.
http://www.pinvoke.net. Avoid the trial-and-error approach to figuring out the VB.NET and C# managed code mapping to Win32 and other APIs; This site allows you to find, edit, and add C# and VB.NET PInvoke
signatures.
http://www.aisto.com/roeder/dotnet. Reflector is a class browser for .NET that allows you to view of your code and all its relationships.
http://blogs.msdn.com/yvesdolc/archive/2004/04/17/115379.aspx. This is a short blog entry, titled “Discussion of Marshal.ReleaseComObject and its dangers,” which talks about the problems with ReleaseComObject()
.
http://samgentile.com/blog/archive/2003/04/17/5797.aspx. This is a blog titled “ReleaseCOMObject revisited.”
http://www.agiledeveloper.com/articles/TDDPartI.pdf. A hands-on tutorial on Test Driven Development (TDD) using NUnit.
http://msdn.microsoft.com/msdnmag/issues/04/06/NET. This is an article titled “Unexpected Errors in Managed Applications” by Jason Clark.
http://blogs.msdn.com/vbfaq. This is a site where you can ask and get answers to many VB.NET frequently asked questions.
http://www.agiledeveloper.com/articles/VSDOTNETCodeEditingTipsAndTricks.pdf. This article shows 25 tricks in Visual Studio to improve your productivity.
3.142.40.56