I am not sure what you mean here, I created 2 sprocs that ran queries and insert/deletes and a user function called from the sprocs that were all static method calls inside a C# class. They all worked fine.

I think what I like about it is the ability to write functions ( in a language I know ) that return a value needed in more complex queries and also sprocs that return simpler datasets that are used to build on to make views and such rather than write it in T-SQL. It goes without saying that accessing UI classes and other more "elegant" .Net members such as multithreading processes would be a no-no but to use this functionality to write business logic would be a plus over having to struggle in T-SQL.

I mean heck, T-SQL is interpreted and procedural and assemblies are compiled and run on a system that itself is compiled assemblies. It would make sense to write your processes in the same environement the server itself runs at a intermediate level. I think MS just doesn't want to come out and sell out T-SQL in lieu of CLR until it is more proven and also as not to upset T-SQL writers and cause a panic of trying to put them out of work, like they tried to do with Fox guys.