I don’t see that Adobe has offered a blog post here yet (though a new banner is showing it), so let me be the first to announce that ColdFusion 2021 has been released today, and yep, the name is indeed CF2021. I’m sure we’ll see posts from Adobe in due time.
Until then (and even after), check out a blog post I did just hours before the release where I list the many, many new features, as I had gathered them from the prerelease (which at the time was open to the public):
The many new and improved features in CF2021
I count nearly 60 of them, and as always they range from the features great to small, any of which may delight you. Go check out the post and get the new version.
Update: I found after writing the above that Adobe had posted the news in a forum post insted:
Introducing Adobe ColdFusion (2021 release)
Perhaps we’ll see a similar post like that from them here as a blog post on the portal, but until then I’m glad to be able to point this out. That forum post does also list and links to resources on the many new features.
Guide
146 posts
requestTimeOut is removed from cfschedule
I’m pretty sure that’s not new to CF2021.
When will the issue with the CF20201 installer and Big Sur be fixed. This is impacting not only my installing CF2021 but also CFBuilder.
Larry, I realize you and others will likely prefer to hear from Adobe, but until they may respond, I have some thoughts that may be helpful.
First, here’s some possible good news: while the GUI or console installer won’t work with Big Sur yet, I suspect the new zip installer for cf2021 would work fine. See the docs or another post here for more on that. It would be great to hear if Big Sur folks might confirm if that works for them now. (See below for why it should.)
As for when we’ll get a new CF installer for Big Sur, we don’t tend to hear dates (or even estimates) from Adobe in advance, as you’ll know from your years with CF. But I realize you’re asking this as much just to remind them that folks are waiting. 🙂
If past patterns hold, it seems reasonable to expect a new installer for the new OS when an update of cf2021 comes out, though there’s no guarantee it would be with the first update.
As for CF2018, I’m not so sure we should expect a new installer, let alone for cf2016 (whose support and updates end in Feb). Often they only do such a new installer (for a new OS) for the latest CF version, even when it’s so brand new like CF2021.
As for CFBuilder, it’s harder to predict. As you may know, Adobe has announced plans to move from an ECLIPSE base to a VSCode base, and they’d indicated that would not come out with cf2021 itself (released in Nov) but after it. No telling if that’s weeks or months out from now. But they may well opt to get only that new version to work with Big Sur, and not CFB2018.
These challenges always happen with any new OS and to users who are compelled to move to it quickly or who buy new machines with it–and not just with CF, of course.
Finally, in such cases, it’s technically not CF or CFB that “don’t work”, but rather the issue is usually with installanywhere software that underlies the cf installers. And sometimes it’s InstallAnywhere that is not updated until the new os comes out, and then Adobe has to build and test a new installer based on that, which adds to the delay.
In this case, it’s just unfortunate timing that Big Sur was released the same week as CF2021 itself.
Hope that’s helpful.
Don’t forget to run cfpm so you can connect to database servers and such.
Just to clarify, that’s only needed if one used the express/zip installer. It presumes to implement almost no packages (to keep it small).
But the normal (gui) installer instead presumes to implement ALL packages by default.
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
