RE: Ektron's .NET/ActiveX Solution

John wrote:

> The latest CMS report from CMSWatch implies that Ektron uses (classic)
> ASP for "scripting" of both 300 and 400 products - is this the case?

To quote my previous posts in which I answered this question:

"*CMS400.NET* on the server is 100% .NET-based.  There are no COM objects or
pre-.NET technologies used and there is no unmanaged code, period."

"*CMS300* has a layer of COM objects underlying everything that allows the
customer to build the web site in Cold Fusion, Classic ASP, ASP.NET, PHP, or
any combination of those languages, and additionally any language like JSP
that support the product's Web Services API."

In *CMS300* the web site itself can be built in the above languages.  The
language we chose to build the 100% browser-based user interface is Classic
ASP (this is why Classic ASP is a technical requirement of the system as
posted clearly and unambiguously on our web site - perhaps that's what
CMSWatch is saying?).  So if you decide you want to modify the open-source
UI layer you're writing in Classic ASP.  But most customers do not do this
and so do not touch any ASP code (unless they're building a Classic ASP
site).  Please note that to translate the UI into another spoken language -
say you're a Kenyan/British firm and you want your African content authors
to see the prompts and system messages in Swahili while the Brits still get
English - you do not need to touch ASP code, Ektron provides a UI
translation tool that translates the UI strings, which are stored separately
from the UI code.

As quoted above there is no Classic ASP code whatsoever in any facet or
feature of *CMS400.NET*.

Tim Denby
Ektron, Inc.