Join the ColdFusion 2025 Beta Today!

[Saurav_Ghosh]

[BETA PROGRAM UPDATE] 4 Dec 2024

• Created a post to announce deprecations and removals in the next release.
• Launched the top contributor contest.
• More sign-ups to the program.
• Added documentation of the earlier drops.

Get an exclusive sneak peek at what’s next for ColdFusion! Sign up for the ColdFusion 2025 Beta Program and get early access to shape the future with us. Engage with the community in the forums, share your thoughts, and keep up with the newest updates and features.

Join the Beta program

Exclusive deep-dive sessions will be hosted by the engineers who built each feature in ColdFusion 2025. 

Check out the session details here.

Join the Beta program and help shape the future of ColdFusion. We're counting on you!

[BKBK]

Thanks for the news. I am looking forward to ColdFusion 2025!

How do I join the beta program? When I click on the link "Join the Beta program" (on this page) I get the error "Sorry! This link is no longer valid".
See attached.

[Saurav_Ghosh]

Let me check that with the team.

[Priyank Shrivastava.]

@BKBK  We are facing some issues in the portal, we will fix it before we drop the build. 

[BKBK]

Thanks, @Saurav_Ghosh and @Priyank Shrivastava. .

[Charlie Arehart]

Bkbk, did you try just clicking the close button? I did and the error went away and I was left at the correct front page.

FWIW, I didn't mention the problem in my first comment because I'd seen Mark Takata acknowledge a similar problem happening last week, but only for current participants in the alpha. So hopefully this affects few who would see this post. 🙂

Anyway,  I see that Saurav and

Priyank both say they will look into also, so sure, perhaps it will be gone soon. In the meantime, can you confirm if you can click past the error? 

[BKBK]

Charlie, thanks for your suggestion. I did in fact go through after clicking the Close button.

In any case, I can confirm Priyank's remark that the portal needs to be fixed. For example, the current title of the program is, "CFNext Prerelease". I would expect to see something like "ColdFusion 2025 Prerelease" instead.

[Charlie Arehart]

Glad to hear clicking through helped. As for the title, well they may or may not see that as something to be changed. Often they have legal reasons not to refer to the new versions name before release.

I do realize they've said cf2025 here. That will be helpful if everyone and everything (including the beta files and installed service names) can refer to it as simply "coldfusion 2025 beta 1". (There's been mention elsewhere, publicly, of another planned beta drop due a month later.) 

[BKBK]

Hi Adobe Team,

It is 2nd December 2024 today. You have been trying to stimulate interest in the launch of the new ColdFusion 2025 Beta. Yet you let stale information to remain for days on the ColdFusion Prerelease websites: 

• "Join the ColdFusion 2025 Beta Today!"
  (on this website since 29th November 2024)
• "Please stay tuned for the impending launch of the open beta (drop 1) on December 1st, 2024."
  (on the prerelease website since 29th November 2024)

This is all stale information. Yet those are precisely the websites that are supposed to generate enthusiasm for the new product.

The issues I pointed out in my previous posts are still unresolved. Though the Beta program, announced to start on December 1, is still "impending", you have said nothing about the delay.

Do you realize just how bad the marketing is that you are creating here for ColdFusion?

[Saurav_Ghosh]

Thanks @BKBK Please check the pre-release portal now. All the builds have been updated.

Apologies for the delay.

[BKBK]

Thanks, @Saurav_Ghosh .

[Sachin Chawla]

Hi Team,

I am getting an error while installing CFNext using GUI Installer (Win64). Attached is the error.

As a workaround installation completed after running the url again -http://127.0.0.1:8501/CFIDE/administrator/index.cfm

btw not able to log a bug on the site as well. 

[dabhat]

DastekSoftwares, thank you for pointing this out. It seems like a cloud setting from your previous version is causing the issue. Kindly log a bug for this and attach the Cloud neo XML files located in the CF's lib. This will help us investigate the issue further.

[Sachin Chawla]

Hi,

Attached cloud neo xml file. Unfortunately, I am getting an error while logging a bug.

Thanks

[Priyank Shrivastava.]

@Sachin Chawla  We logged a test bug and we are able to do that. Can you please try again, if it doesn't work, we can get on a call and help you.

[Sachin Chawla]

Thanks @Priyank Shrivastava. I am able to log a bug now - CF-4224685

[Priyank Shrivastava.]

Thanks, Sachin for letting us know.

[dabhat]

@Sachin Chawla This appears to be an issue caused by the migration. I noticed you've logged a bug, but I'll need the Neo files from your previous version to reproduce the issue. Could you please add that information to the same bug?

[Sachin Chawla]

Hi @dabhat Attached neo file to the bug from previous cf version 2021.

[rickmaz]

Does anyone know how we update the beta when updates come out? do they show up as updates (likely not) are we alerted when new builds come out? do we have to re-install the new build?

[Priyank Shrivastava.]

@rickmaz We will share the update when the next update will be available. We usually share the refreshed build for Beta's next release. 

[BKBK]

The download links include the following:

VS Code Update
VSIX file to update VS Code to support CF Next'

However, that download does not contain any file of type VSJX. 

Does the developer have to undertake further steps to obtain a VSIX file? If so, please explain, adding the necessary steps.

[Priyank Shrivastava.]

@BKBK  Please download the .ZIP and rename the extension to .VSIX. 

Launch the VS Code and Install it from extension. 

Select this VSIX file and it will install the extension. 
Please let me know if you have any problems.

[BKBK]

Thanks, @Priyank Shrivastava. . 

[BKBK]

Hi @Priyank Shrivastava. ,

On the Prerelease website, the current instructions for installing the VS Code extension are still unclear. That is partly because the word "extension" has a double meaning in this case.

Please replace the instructions with something similar to what you've given here:

1. The VS Code Extension for ColdFusion Next is offered as a .ZIP download. Download it .
2. Change the file-extension from .ZIP to .VSIX. 
3. Launch the VS Code program and use the .VSIX file to install the VS Code Extension for ColdFusion Next.