MSDN articles on Generics
These articles my be useful if you want to extend your knowledge about .Net Generics
from Juval Lowy.
[Via Dave Burke's Blog]
Palermo .Net Scripter
Run .Net console class as batch files from the command line with this utility that will compile and execute any code file (that ends with .cs, .vb, .js). Supports C#, VB.Net, and JScript.Net.
[Via Jeffrey Palermo blog ]
What log level to use?
A Severity Level (def) is a quality of a logging message. Assign a severity level to every logging message that you emit from program code.Having severity levels assigned to logging messages allows filtering out messages
that are not of interest. The following severity levels are provided:
- FATAL: means that an exceptional context/event will lead to a process termination. In EL4NET, errors in config and early components initialization errors are fatal.
- ERROR: means that an unexpected issue has occurred. In EL4NET, unexpected exceptions are logged as errors. A generic swallow (i.e. with generic catch clause) should use this level.
- WARN: means that some rare event occurred which might be an issue but doesn’t have to. In EL4NET, a recovery mechanism makes that a lazy component that fails to initialize and that later succeeds, leads to an exception the first time, and a warning the second time, saying that the component is already created but not initialized.
- NOTICE: used for logging important state of the system. In EL4NET, status is used to notify when all static components are loaded.
- INFO: used for logging internal state of the system. In EL4NET, info is used to notify when one static components is loaded.
- DEBUG: used for debugging/development purpose; may very rarely be used in operational scenarios to state the system. In EL4NET, debug is used to display proxy generator steps.
IntelliSense style word completion for MS Query Analyzer, VS.NET
IntelliSense style word completion for MS Query Analyzer, VS.NET 2003, SQL Server Management Studio and VS 2005. PromptSQL, from Atadore, works with:Microsoft Query Analyzer,SQL Server Management Studio (Microsoft SQL Server 2005 CTP),Visual Studio.NET 2003 Visual Studio 2005 (Beta 2).It adds IntelliSense(r)-like word-completion for you when you are editing SQL using these products.
XP Burn Component
The XP Burn Component allows your .NET applications to burn files to CDR/W discs on a Window XP or Windows 2003 Server system. This component does not work for systems which have a different OS installed; though it will detect that case and give a reasonable error message. This component talks directly to the system IMAPI interfaces and does not use the Windows XP CD burning wizard, so its possible to create your own snazzy UI for burning CDs.
Though the component is a UserControl, I wouldn’t recommend that you put it in the toolbox. Instead, simply reference it and use it like you would use any other framework type (the constructor can potentially throw exceptions, so for robust handling you should wrap it in a try& catch). The documentation and source for the component is included in the download.
Download
XP Burn Component, Documentation and Source
Download and run the MSI for this component to install the documentation, source code and assembly.
