Andrew's ramblings

Coldfusion and .Net integration

Tags: Coldfusion

Now either I am missing something or I am missing something.

One of the things that .Net is capable and very legal is to either have a getter or a setter and even both. But for some reason in ColdFusion if there is one of the set/get is missing ColdFusion will generate an error.

This may not be a ColdFusion bug, but it certainly is related to the jnbproxy that ColdFusion uses. This causes major issues when using most .Net assemblies because I guarantee that there is about 98% of assemblies that will have either one getter or setter and not both.

One such example is the new asReports that I am working on, due to the fact that I could not load the assemblies directly into ColdFusion and write ColdFusion code to do what I needed. I thought the best thing then would be to write the whole thing in .Net itself.

So many issues.

First issue I came across. Was that one of my properties only needed a getter and I ignored the setter. In my test application for .Net it works a treat, but in ColdFusion you get this weird error

CreateProcess error=206, The filename or extension is too long.

So that's ok, create a setter that does nothing and away we go. Sure I thought everything works fine.

But then I came across another error.

CreateProcess error=206, The filename or extension is too long.

And this time I have no idea what the hell this means, the assembly is CrystalDecisions.CrystalReports.Engine.dll I even tried to copy it to the directory I am running the website from.

To no avail, same error as before.

As much as I think that the idea to run .Net assemblies in ColdFusion 8 can be great, it has too much work needed before it can seriously be used.

I even have a compiled assembly that will work on 2 machines, both being 32 bit OS's but the 3rd being a 64bit OS I am having no luck what so ever.

I have no idea if the guys at adobe tried enough scenarios, or even in beta testing people tried enough. Either way there are some serious issues that seem to trace right back to the jnbproxy.

ok now to try BlueDragon?

Tweet