.NET integration

Adobe® ColdFusion® is a Java™ application, so ColdFusion applications run on leading J2EE application servers as compiled Java bytecode. This Java DNA makes it easy for you to natively integrate existing Java assets/objects into your ColdFusion applications. But what if you're developing with Microsoft .NET? In previous versions of ColdFusion, there was no native way to integrate those assets into a ColdFusion application. You could use web services to integrate ColdFusion and .NET, but that technique often suffered from poor performance or compatibility problems. ColdFusion 8 software solves this problem by introducing native .NET integration that lets you access Microsoft .NET assembly classes as CFML objects. With ColdFusion 8, now you can leverage .NET objects as easily as Java assets.

.NET Integration

The .NET integration capabilities of ColdFusion 8 do not rely on .NET remoting or web services, so no changes to existing .NET assets are required. The .NET classes that your application uses do not have to be local, so your ColdFusion application can access .NET components that are on remote systems, even systems that are outside your firewall. Also, the ColdFusion system does not require .NET runtime software installed to use remote .NET components, so ColdFusion 8 running on a UNIX® , Linux® , Solaris™, or Mac OS X system can access and use .NET assemblies elsewhere on the network. ColdFusion 8 even converts data types automatically, so you don't have to take any special steps to ensure correct conversion among ColdFusion, Java, and .NET data types.

.NET integration

Next steps