Well, at the very outset, you should not be using the SqlDataSource in a production environment at all. It is only intended to easily demonstrate concepts to newbie developers, since production level software rarely use SQL queries embedded in code. Use an ObjectDataSource or roll your own DataSource and create stored procedures.
As for the formatting, it follows the trend set by MS - "Our IDE writes better code than you, so we're going to write it our way." On Sep 2, 9:13 am, Chuck <[email protected]> wrote: > Hello everyone, > > I've had a minor problem that has only recently started bugging the > heck out of me due to annoyance, and I would really like for it to > stop. I'm using Visual Studio 2005 at work (mainly ASP.net 2.0 and > C#). I've been using the sqlDataSource objects without a problem to > connect to our databases for 2 years now and do it quite easily. > HOWEVER, when I have a hefty nested where clause in my sql query that > includes many and/or filters, the wizard seems to want to rearrange > them after I finish setting the sqlDataSource up. I then have to go > back and fix the query the way I like it, after the fact. Granted, it > still works either way, but I like to have a specific format on my > stuff for readability purposes. Is there some setting that I need to > change to keep that from happening? Is there a reason behind why the > framework wants to change it? I've searched a little and haven't > found anything yet. Any advice would be greatly appreciated.
