So, I get that M$ thinks their software writes software than us. Meh. I can just change it however I want to after the fact.
However, seeing everyone's posts and a few links of reading puts me in a position to ask other questions I never thought would come up in the first place! LOL (does this bear another post, btw?) http://www.theserverside.net/news/thread.tss?thread_id=29919 http://msdn.microsoft.com/en-us/library/ms379547%28VS.80%29.aspx The main downfall I see happening with SqlDataSource seems to be the mixing of different layers. I suppose that's about a good enough reason to change control types for the sake of readability and debugging issues, as this goes with my original post anyhow. With that being said, are there any other issues I should be worried about when using the sqlDataSource object? Am I safe using them to bind dropdownlists for data display issues? Do they cause any connection or performance issues that seem to disappear with the use of an ObjectDataSource? Admittedly, I know nothing about the ObjectDataSource (and will be learning a lot about it shortly), but should I dispose of using sqlDataSources altogether? I ask these questions because I've heavily depended on the sqlDataSource for a lot of my tools since I've been programming, and for the most part, haven't had any issues, other than the occasional time out issues. On Sep 2, 6:16 am, Cerebrus <[email protected]> wrote: > 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.
