Google Groups 2 BETA offers Atom feeds for each group. To see feeds for a specific group, use this format:
http://groups-beta.google.com/group/NAME-OF-GROUP/feeds
Here are a few examples:
http://groups-beta.google.com/group/alt.www.webmaster/feeds
http://groups-beta.google.com/group/alt.html/feeds
“Although .NET provides a number of quick and easy ways to serialize and deserialize data, do not use them. This article explains why. “
“This add-in for Visual Studio (7.0 or later) communicates with www.pinvoke.net, making it easy to copy signatures and types from the PINVOKE.NET repository into your source code. It also highlights alternative managed APIs that help you avoid PInvoke altogether, and makes it easy for you to contribute your own signatures and types! Because the latest information in the repository is displayed, the number of signatures and languages supported should grow over time. This also means that an Internet connection is required to make use of the add-in (although it behaves gracefully when no connection is present). Defining PInvoke signatures (also known as Declare statements in VB) without any help is an error-prone process that can introduce extremely subtle bugs. It’s time to stop writing PInvoke signatures from scratch! Instead, copy and paste your way to productivity! Think of this as the 21st century version of VB6′s API Text Viewer. For more information, visit www.pinvoke.net. “
Learn how to provide templated URL driven content with HTTP Handlers, using three real-world scenarios presented in this article.
Reflector is a class browser for .NET components. It allows browsing and searching the meta data, IL instructions, resources and XML documentation stored in a .NET assembly. Reflector was first released in October 2000 running on .NET Framework 1.0 Beta 2.
Code Model: While previous versions of Reflector partly used the CLR Reflection infrastructure, the new version 4.0 has changed to use a code model library for reading assembly files into memory. As a result Unload and Refresh operations really unload files from memory and Reflector is no longer locking files on disk.
Reflector and .NET Framework 2.0: Reflector.exe runs on all .NET Framework versions. The new code model library loads .NET Framework 2.0 assemblies with no .NET Framework 2.0 installed. However, a Reflector.exe.config file is still going to make Reflector run faster on .NET Framework 2.0.
Assembly Cache: When resolving an assembly reference, Reflector will first search the local path and then falls back to the cache directories defined in the Reflector.cfg file. Reflector doesn’t search the GAC unless you add ‘%SystemRoot%Assembly’ to the cache directories list.
Search and Callee Graph: There is now only one search window (F3). You can click on the icon on the top-right to switch to search members (this was previously called member search). The reference search windows are replaced with a callee graph window that shows any kind of dependencies of a type or member.
Command Line: The /configuration switch allows you to specify a config file different from Reflector.cfg. The /fontsize and /fontname switches can be used to increase the font size for overhead demos.
Assembly Versioning: By default, assembly version numbers are ignored when resolving type and member references. You can enable side-by-side versioning in the options dialog but it is suggested to avoid this if possible.
Add-Ins: Reflector add-ins and hosting projects can be found here. An introduction to the add-in model is available here.
WinFX Help: To view the Longhorn MSDN documentation instead of the .NET Framework MSDN documentation add a [WebSearch] section to your Reflector.cfg file with Msdn=”http://longhorn.msdn.microsoft.com”.
The most recent version of .NET Reflector is available here.