We are happy to announce the
first release of Migration Guide for ColdFusion 11. This guide will help you,
to migrate your ColdFusion 9 and ColdFusion 10 servers to ColdFusion 11
seamlessly. This guide also gives a fair overview for migration of legacy
servers to the most recent and supported versions. This helps you understand
the various phases of migration, along with, how to use Code Analyzer. The Code
Analyzer reviews the CFML pages that you specify and informs you of any
potential compatibility issues and ensures a smooth migration.
We also tried to cover, few of
the common migration issues and possible solutions.
Here is the link to ColdFusion 11 Migration Guide and don’t
forget to visit the “Help and tutorials” section inside the guide.
We are open for your suggestions
and feedback.
Staff
9 posts
It’s just that Adobe believed that they would’ve killed off ColdFusion before the Windows 10 release. They’ve certainly tried their best.
Some of us are way too busy to do your job for you. This process should have started when Windows 10 first went into Insider Preview. I’d be surprised – very – if not a single Adobe ColdFusion engineer did not try the Insider program since LAST YEAR and has only now – nearly TWO MONTHS since RTM release discovered that none of your installs work like they should – in fact even Raijin Alpha 2 is released minus the 6 major CF11 updates. What’s the go there?
@Peter, could you please respond on the bug (https://bugbase.adobe.com/index.cfm?event=bug&id=3984812), with the details and the error message (if any).
@Shawn, the team is working on that aspect. Till then, please try the manual connector approach.
And for me it didn’t even fricking work.
I was already aware of it. The point of my post and his suggestion was not to lag so far behind every version. They have beta programs, use them. Stop assuming everyone is a late adaptor.
Hi Peter & Shawn,
There is already a blog post available at https://coldfusion.adobe.com/post.cfm/configuring-connectors-manually-for-iis-10 for configuring connector with IIS 10 (yes, manually as of now). Please refer to the same.
I agree with Peter, CF needs to be faster integrating with new versions of Windows. Seems like we do this dance every version.
Like how long was Windows 10 in Preview before it’s release OVER A MONTH AGO! I’ve been using it since October 2014 – not with ColdFusion of course due to the fact that in the almost intervening YEAR Adobe did absolutely NOTHING to get current builds of ColdFusion CF10 ready. I say again – Adobe did NOTHING! Which is of course they are famous amongst us CF developers for doing – 20+ years myself.
Hi Tom,
You can refer to http://www.adobe.com/devnet/coldfusion/articles/coldfusion-tomcat.html for aliases and default directory syntax.
Did you mean to have the comma in “cfide,/” in the aliases?
Tried that variation of the “/” and also did not work. I’ve logged a bug as requested. Thanks for quick response.
Justin, ColdFusion 11 is not yet certified on windows 10. But, this should work. Can you try the following and restart CF service?
In case, it still doesn’t work, please log a bug at https://bugbase.adobe.com/, and the team will look into it.
I’ve installed CF11 developer onto my local network and trying to redirect the default directory on Windows 10 platform. I activated the tag in the server.xml file, and pointed aliases to installed location. Neither the alias or program file locations are working. Ideas?
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
