Recalling pieces of what Reuven and Don wrote, I think you will have lost the battle if your discussion is framed as "OpenACS vs .NET". A better comparison would be "IIS plus the .NET class libraries vs. AOLserver" or "OpenACS vs.
iBuySpy". The problem with talking about "OpenACS vs. .NET" is that the average tech person has a much better idea of what .NET is than they do what OpenACS is. So your audience is likely to equate "OpenACS" with "the AOLserver Tcl APIs" which does a vast disservice to the gobs of functionality, field testing and peer review that OpenACS has under its belt.
