Bill, >While you can get away with "<%%>" on a page, this >is very much "frowned upon" in the brave new .NET world. Are >you still using scripting?
We have product to get to market. I still use <%%>. Frown away. >Have you converted to using VB.Net or C#? Both. VB.NET is so close to C++/C# that I don't even think in terms of language any more. I just see a problem...engineer a solution...implementation language seems irrelevant any more...It is indeed a brave new world! >Are you using server-side controls? No. But we are using Web Services >We wanted to use ADO.NET,... one could do what you suggest and then >begin to implement ADO.NET ... You are correct...code every thing in ADO COM now. Then upgrade to the faster ADO.NET one module/sub-routine at a time. ADO.NET has a fantastic assortment of Database caching, recordset and Cursor options that allows us data driven web developer types awesome flexibility in how we interface databases to our CMS solutions. You will need time to learn how and when to use all the new caching options..to squeeze every nanosecond out of ADO.NET! ADO.NET using the Native SQL 2000 connection is faster than ADO using COM. Tony -- http://cms-list.org/ trim your replies for good karma.
