After speaking to a few other people in the community, it seems like there is a bit of confusion about the update to ColdFusion Builder. We (Adobe) can probably do a better job on the web site making this clear, but in the interim, let's clear up a few things.
-
The latest version of ColdFusion Builder is 2.0.1. The last main release was 2.0, and we had an updater after that.
-
If you go to the web site, you only see "2" mentioned. I think that's probably fair, but, again, it may not be obvious to existing users.
-
So how do you upgrade? Unfortunately, you cannot use Eclipse's built in tools to update. You have to redownload the code from our site. How? Just download the trial again:

I thought you had to uninstall the previous version, but Charlie Arehart let me know that you do not need to do this. The installer will recognize the previous install and upgrade it.
-
So what's new? Lots of cool stuff. Here is a link to the docs pages for new features in 2.0.1. Extensions got a lot of love in 2.0.1!
-
Hey - you can still run it for free. Again, you can run ColdFusion Builder for free. I know I keep saying this, but people forget it. Yes, it is a "reduced functionality" version, but if you need more time to determine if you want to purchase the tool (and we give you 60 days!), then you can continue using the product past the trial period.
Archived Comments
Well on the Mac you have to uninstall and it appears that I have in fact lost my third party add-ons like Subversive.
If you uninstall it would remove everything. Odd - well - I was just passing on what was told to me I did uninstall too, but only because I had the beta.
Fortunately after reinstalling Subversive it was able to recover all the repository information.
Does anybody know if the Express version (what you get after the 60 trial) is free for commercial use? I searched high and low (including the EULA) the other day and could not find the answer.
As far as I know there is no restriction, but I'll ask the boss.
Thanks Ray... I just downloaded the latest version and tried it out. I see they did some work on the Find Dialog (ColdFusion Search) and fixed some major bugs that prevented me from upgrading. However, it really bums me out that the Find Dialog is re-centered in my workspace each time I select some text and hit CTL-F. Who keeps the Find Dialog front and center? I usually move it to the side and do my work. This is killing me!! Does this happen in your world? I'm using Win7 x64. Why can't they get something so simple and core to editing to work correctly.
I added a bug:
https://bugbase.adobe.com/i...
Please vote on it!
Jake, you can continue to use the express edition for commercial use as well. There is no restriction on that.
Ray,
what about cfb 2.0.1 and colfusion 10? is the ide ok or have we wait for an update?
regards
Sal - not sure what you are asking. If you are asking if 201 works with 10, then yes. I said above my favorite feature was the extension updates, but there were other things as well, including CF10 support.
Basically:
CF10 + CFB201
is the combo you want. Even if you aren't on CF10, you still want CFB201. It it the best version available.
JP - I'm one of those people who keep it centered. :)
Ray,
i've cfb 2.0.1, and now i'm sure i can start writing cf10 code.
thanks and regards
I'm on the "dark side" so with this release and the new Data_Type Token for built in functions, UDFs and CFML variables I've been using a "peach" like color (RGB: 255 172 132). It's a decent syntax highlight color as to not blend with ColdFusion's "light yellow" attribute names and "yellow-orange" CFML tags and JavaScript's "light red" integers and "light pink" booleans that are the default in Aaron Greenlee's post at http://bit.ly/Kxo8Dt.
Maybe folks would agree that if a user moves the Find Dialog, it should stay where it is. CTL-F is a shortcut that should only focus the dialog and backfill the search text, exactly the same way as every editor I've worked with, including CFB 1.0, which uses the Eclipse Find Dialog.
I've never met an editor that re-centers the Find Dialog after you move it. Even if this isn't a problem for you (because you never move the Find Dialog??), maybe you would agree that re-centering it is the WRONG thing to do, and is, in fact, a usability bug.
Please vote on the bug here:
https://bugbase.adobe.com/i...
Has anyone else reported issues installing CFB 2.0.1 on a Mac? I just installed the new version and when I launch the app I get this message "The CFBuilder executable launcher was unable to locate its companion shared library."
JP, there was already a bug for this: https://bugbase.adobe.com/i...
It's perhaps best to not suggest splitting the votes for it (not that it has many votes).
I consider this issue to be one of the more significant usability problems with CFB. It's *such* a PitA. Unfortunately Adobe didn't seem to think it mattered. I guess this might be because their engineers don't use CFB, they use vanilla Eclipse (I'd assume), and vanilla Eclipse does it right.
--
Adam
Let's be fair, Adam. I think the engineers would like to correct each and every issue and support each and every feature request. There simply isn't enough time. Just because an issue you care about is not addressed, it does not imply they don't care. Yes - I'm expected to back up my coworkers, but it's honestly how I feel. Shoot, there was at least one bug in CF9 that I cared about that didn't get addressed due to time issues. Do I think they don't care about me? Nope.
Ray, I was referring to a comment Evelin (from the Adobe CFB Team) made against the ticket.
--
Adam
At the end of the day, the engineers have to prioritize how important somethings are. My point does not change. You may think X is super critical. The engineers (who are NOT always right, but who DO, typically, have a broader idea of the scope of issues and the amount of work) may think X is not critical.
I will add - you are right that people should focus on one bug. The more votes, the more the level of important may change. JP, if you did raise a bug, you may want to add a comment saying it should be closed and point them to AC's bug.
Thanks Adam... that original bug was the one I created back when I first evaluated CFB2. But because it was closed, I thought I needed to create a new one. I can't re-open the bug, nor can I vote on it, so I figured by creating a new bug I would draw attention to this (in my opinion) HUGE usability problem. I use CTL-F all day long, and I think most editors got this right back in 1990. It makes me not want to spend the money to upgrade and it makes me somewhat embarrassed to say that I'm a CF developer (amongst my .NET peers)! I guess I feel pretty strongly about this issue!!!
Anyone else experiencing an issue installing CFB 2.01 on Windows 7 Pro SP1 64-bit? I downloaded the file fine, but when I attempt to install, it asks me to "Please select another location to extract the installer to:". I've tried selecting several different locations, before and after restarting my PC, but it just show shows the same dialog.
That's my platform and I'm not seeing it. Sorry.
Same here... I didn't run into that issue. The installer updated my previously installed version of CFB 2.0.
Thanks. Turns out the download was incomplete. The browser appeared to download the complete file and it opened fine, but then I realized the file size was way off (only like 266MB). I re-downloaded and installed fine. Thanks again...
Web development would be a heck of a lot easier without browsers.
@Joe, did you solve the installation problem for CF Builder on the Mac? I'd like to update, but I'm very reluctant if updating would hose CF Builder completely.
I have not yet. I actually just reverted back to the older version until I have an opportunity to mess with it again. I'm not sure if others are seeing the same problems with the Mac install or not.
@Raymond, It would be easier without IE for sure.
For those on a Mac, I was able to get the new version installed. I had to re-download a fresh copy from Adobe's site. The .dmg file still threw an error with an invalid checksum but you can click skip when you first run the installer to bypass the checksum verification. I did that and it installed correctly this time.
I'm getting the same message as Eric on the same platform except with CF 10 developer edition. Seems there is an issue with InstallAnywhere. I tried closing out of everything, re-downloading it, and making sure it was running as admin, but nothing seems to work, and chose different locations. It gets to 100% and then displays the message. Oh well, I think I have my CF8 installer lying around here somewhere. I'll wait until Adobe gets the bugs ironed out before I try again.