I agree with all of you guys. Usually the SMO is the best option in C#, but sometimes, we already have the stored procedures done. If we already have T-SQL code done, there are alternatives different than the SMO to execute and call SQL Server using C#.
In my case I had a customers with 300 stored procedures used and already created for administrative purpouses. He wanted a custom C# application with nice buttons. If he already had stored procedures, it was not smart to create SMO code.
We have to learn different alternatives and we do not have to close our eyes because one problem can have multiple solutions.
I guess my solution will help to all the guys who do not like SMO and they have T-SQL experience and code already done and they just need to create an application quickly in C#.
There are many topics about SMO, so I did not find any reason to write about it again.