.NET compliance is a pretty vague term. The people asking about compliance
will need to be more specific.
ColdFusion is built with Java - so it could be said to *not* be .NET
compliant.
Now ColdFusion does have varying degrees of .NET interoperability though web
services and other third-party tools (such as Black Knight that provides
some .NET extensibility).
The New Atlanta folks do have a .NET version of their BlueDragon server
currently in beta. This generate a slight problem though. The BlueDragon
JX (the Java version) provides compatible functionality to CFMX but that is
not wholly so with BlueDragon .NET. The .NET version does provide all the
CFML and most all of the expected functionality - but you cannot run
Java-based components with BlueDragon .NET.
You options are a Java solution, providing connectivity to .NET though
external mechanism (such as WS or Black Knight) or a .NET solution that
requires Java connectivity though an external mechanism.
rish
-----Original Message-----
From: Kurt Knazek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 27, 2004 11:55 AM
To: CF-Talk
Subject: .net compliant (ot)
We are a cold fusion shop and have been asked about being .net compliant.
What does .net compliant mean ?
Thanks
Kurt
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
