Tony - We have taken the same approach to implementing user defined controls when we were putting the new site together, as we were building it based on templates from a design firm. I want to understand, however, how you reuse your old ASP. While you can get away with "<%%>" on a page, this is very much "frowned upon" in the brave new .NET world (and it actually causes some problems in places, depending on what you are doing). Are you still using scripting? Have you converted to using VB.Net or C#? Are you using server-side controls? This is more of a curiosity so I understand the approach you took.
We wanted to use ADO.NET, and we coding all the functionality in C#, and we were coding new, so it was not such a big deal. An approach that seems to suggest itself is that one could do what you suggest and then begin to implement ADO.NET in sections to move the entire app into .NET. Sincerely, Bill Schneider Director, Content Management Ness Technologies www.ness-usa.com 703-464-0133 x125 703-464-0138 -----Original Message----- From: Tony Leotta [mailto:tonyl@;pillarsoftware.com] Sent: Friday, November 08, 2002 3:28 PM To: Schneider, Bill; 'Andrew Iddon'; ''Cms-List (E-mail)' Subject: RE: [cms-list] MSCMS 2002 >>>Unfortunately, due to the way ASP.NET works (e.g., code behind), you will >>>need to rewrite functionality to move your site into .NET. This is true...however...I am converting existing ASP Modules into User Defined Controls and including them on pages.. I have found that by using this technique I do not have to rewrite that much code. In fact...I have already developed a few very good methods of reusing nearly 98% of the old ASP code under .NET. (This means NOT using ADO.NET!) Tony -- http://cms-list.org/ trim your replies for good karma.
