I've been doing Windows Forms work in .NET 2.0 and only doing ASP.NET 2.0 for the Web Services app that supports the Windows Forms app. For everything else on the web I've stayed with .NET 1.1. I'll move to .NET 2.0 when we're Golden, but let me do my job in 1.1 for the moment, thanks. ASP.NET 2.0 is awesome and glorious, I'm sure, but no project files, having to publish my web app everytime I need to update it is just too much PITA Bread for me. And I love starch, it's my favorite food group.
No one can question my ADO.NET 2.0 Love though. Still, that weird ASP.NET 2.0 publish-me-if-you-really-love-me, WSIWYG world cut me deep this morning and inspired this Tip of the Day.
I updated the web services app for my Windows Forms app and got an ADONET Connection Time-Out error when running the .ASPX test page I use to test the Web Service. I initially thought I forgot a Grant Exec or forgot to add a View or something, but that wasn't it. Fortunately I had dealings with ADO.NET Connection String Stings in the past, so I went to the [schweet] ADO.NET 2.0 Designer and scoped my newest Data Adapter and DataTable Adapter.
There it was. The new daResources adapter was using the application property (by default, apparently--in blue) rather than the Old School web.config connection string (in red.) When uploaded to HQ, the Web Services app was trying to hit my development SQL Server. Nadda. Using the web.config (still a good idea 5 years later) gave me the ability to hit the correct server for the application's environment rather than being compiled into the ASP.NET 2.0 binaries.
So there you go. Give me a word...any word...and I will show you how the origin of that word is Greek.
