Hi Greg,

Very interesting. You know...just becasue something is an exception to the rule - it does not mean it is "wrong". Clearly, you have given this a lot of thought. FWIW, if your ASP framework is working fine as-is, looking at things from a pragmatic perspective, there is no real need to move it to .NET in the first place - at least not in the near term.

Good luck..



>John,
>
>
>>>
>>I was not 'porting' my ASP app to .NET at all. I was looking to re-design from the ground up in .NET but just could not create a methodology that was easy for non .NET developers to work with.
>>>
>>
>>Perhaps the issue is that .NET has progressed a bit beyond the art of copying and pasting code...
>
>I agree with that completely. .NET has a more strict methodology to use it properly.
>
>>
>>
>>I applaud you for your accomplishments... Yours is the first argument that I have heard that bills ASP has being easier and more efficient than ASP .NET.
>
>I finally remembered one of my main .NET stumbling blocks. Adversting code provided by Linkshare and other affiliate programs includes fraud protection for their forms. Re-directing through your website voids the commission for many of their best advertisers. With ASP it didn't matter because ASP has no methodology for it's use that cares where you send your forms to.
>
>.NET wants forms to re-direct through your server, period. That is what gives .NET so much power.
>
>One possible work around I had cooked up was to use Javascript to change the form action tags on the fly in HTML so that advertiser related forms would go directly to the advertiser and not redirect through the server.
>
>Just like everything in life there is always a workaround. I'm still convinced there is a way, but it was the external advertiser content and how it could conflict with .NET's form methodology that made it tough.
>
>I want you to know that I realize 100% that my solution is the exception, not the rule. For most web development work I'm sure .NET smokes ASP and I've never said otherwise.
>
>
>Greg