SQLConnection Objects Declarative vs C# code
<p>I am curious about developer opinions regarding creating and using SQL connection objects.  </p>

<p>We are transitioning our software application from ASP to ASP.Net, i.e. new features are being added using .Net.</p>

<p>We have created SQL Connection objects through C# code and and through the designer which declares the connection object in asp markup.  We've also created the connection object bypassing the designer and just coding the asp markup.  We can add parameters and SQL statements to the asp designer/markup that make the connection object quite usable for the application... or we can do this through code.</p>

<p>What are the opinions of experienced .Net developers on the options for creating and using the connection object.  Pros/cons for using c# code vs. the asp interface (design tool and markup).</p>
