Yep that sounds about right to me, except it seems a bit simpler to use. Anyway I'm convinced of its benefits, not something I'd use that often but when it's used it seems like it would be of great use.
I think the article is fine, but it seems to ignore the Visual Studio 2005 tools that can make the process of creating and debugging SQL CLR exectuables far easier.
Excellent article!!! I am new to SQL Server and am charged with moving a MS Access application to SQL. I have managed to get all our business rules translated to the point all MS Access is used for is a "front end" consisting only of a database full of forms. Part of our application requires the output of reports in an Excel format. A resonably easy task in VBA. I have been struggling on how to accomplish this in SQL Server 2005. Since I am able to create the customm reports using VB.NET or C# .Net, this article gave me the link I desparately was searching for!
My Kudos to the author!
