Why can't I work with ColdFusion documents?

Just in case Adobe is still listening - yeah, i know it is 2 years later... And my cfm pages render fine in code view, and i know i can open .cfm natively. yay.  But i can't create a "new" cfm document?  how is that not an option?  and how does Emmet syntax (which is awesome) only work with PHP and not CFM? and oh, one more thing, the adobe coldfusion licensing team tells me i need 12 licenses for CF11, though we needed only 1 for CF9.  So adobe - the ColdFusion conference is one week away (November 9-10, 2015, Vegas).  Are you guys prepared to answer these types of questions?  Because they will be asked.  I know because I'm attending.

Wow, a few years later.. this thread resurfaces. I felt that change indicated that CF was no longer even being actively used at Adobe for any of their projects - because you would figure they would have caught that if they did. It was an easy fix when you found the file to mod... they just removed the functionality of being able to click and open a coldfusion document. That indicated to me that someone had to edit that file and remove that code. That meant someone was told to do so, indicating what I felt was a general shift in the wind away from that technology. I moved every site I had from CF as I took it as a sign that it was on the way out. Whether it was or not is a moot point because I no longer have a single site running Coldfusion nor do I have a single project that uses that technology.

This entire topic is BS!

Adobe..... support your own products with your own products and stop forcing us to use new products that aren't included in our CC subscription.

Most of us in here have been loyal to DW and apparently CF for many years, show your loyalty in return!

While I understand CF is the programming layer and DW is more meant for UI, even the UI developer needs to manipulate the .cfm pages.

If you don't want to support .cfc in DW, ok, that I can swallow, but to remove .cfm? Are you expecting the UI developer to move to CFB too?

FYI... for many versions now if you converted a .cfm page to a DW template, the file was saved as Template.dwt.cfm.  Guess what... you have destroyed my ability to manipulate templates for every site I manage.... thanks for that.

If you are going to replace one IDE with another, make sure they can do the same things.  The way you have to go about using SVN in CFB is silly, if you can integrate SVN with DW, you can do it for CFB too.

Come one guys.... this one is ridiculous!

Wake Up Adobe!!!!

You can clearly see that there is a big community of CF Developers who many of us have built entire businesses on Coldfusion and depend on it! Not being able to open a .cfm file from a product that is your own on a language that is your own is a shame. I am sure that 90% of developers know how to change a file association to an extension and can figure out the workaround, that is not the issue I think. The real issue is that you are putting out on the market a software that many developers work on daily basis that suddenly can not even create or open files from your same company. When it is something that can easily be included in the core configuration of the software.

The other important question is> What is next? Is Coldfusion dead?

I think Adobe still at this point has enough time to rethink their strategy and make us all CF developers happy again by AT LEAST not underestimating and forgetting the Coldfusion presence on their own aplications.

One of the main reasons for us to get the coldfusion server was because it promises the compatibility and ease of use with the rest of the Adobe family, we are and have been willing to pay for the server and not move to a free platform like php because we are Adobe believers, but this in my opinion speaks VERY bad about Adobe.

I sincerely hope that someone can offer me a solution to this latest (and quite frankly greatest hiccup in the world of coldfusion for me). I NEVER post on blogs, forums or otherwise as I can usually find what I need to know if I look around but this is not the case. I was anxiously awaiting the new cc for dreamweaver since the purported tools that would make my development much more integrated with the latest methods only to discover this morning that there was absolutely no coldfusion "anything" in the program. I thought it was the way I set up the panels. But nope...

Now I installed cfbuilder. ok, fine it will cover all of the "programming" part of coldfusion and it looks like it will do that better. I get that.

BUT, how exactly do you take the "ugly" stuff that cfbuilder will help me build and actually turn it into a website that the latest trends require? I understand that I can open the file in dreamweaver and make it "pretty" but the real issue is that so much of the time the "application" that I am building is very much a part of the "website" that I am building - ok, ALL the time. What exactly is the commonly accepted workflow that will make this whole thing flow properly without having to switch between completely different applications all the time.

My issue is that maybe I don't understand that cf is a website language for displaying on web browsers, or am I wrong for the past 10 years...

Yes, I develop "applications" that are not pretty sometimes for the customer that needs a program made for them custom, but that is so rare that it does not accompany a website that holds it all.

How is this accomplished? I know I ramble and I hope I got my point across. Can you help me with finding a solution that will allow me to continue to use coldfusion in beautiful css and jquery websites as my customers have come to expect.

Please reply?

If you are looking for a free CF application, there is CF Builder Express:

http://www.adobe.com/go/trycoldfusionbuilder

Gives you all features for 60 days, then reverts to Express version.

My two cents on the dilemma... well, my solution anyway:

http://trendecide.com/entry/adobe-cc-deprecated-me

Adobe, I'm not sure what is up with you these days. You've killed the visual designer in the latest version of FlashBuilder (4.7) that's available via Creative Cloud, and removed access to FB 4.6 as well to your CC customers. You've now killed a design tool for CF coders. You will be killing access to Fireworks sometime in the next 12 months for Creative Cloud customers. What's next? You've got a large, loyal base of developers that have worked with your software and languages for many years.  You're doing a great job of alientating that base over the last 12 months. My suggestion: just go ahead and get it over, instead of doing this slow bleed. Kill Flash. Kill CF. Just be done with it.

Crazy.  This is the end for us and Adobe ColdFusion.  We will be cancelling our Adobe subscriptions for our entire team. Really poor decision to alienate the very core of your development population.

S.

WOW. As a CF person from the Macromedia days I am shocked Adobe has removed CF support in DW CC. That is just plain stupid. I just begrudgingly moved to CC because it felt like I had no other option since everything is going CC and now you remove CF support (your own language) from your main development product? I don't want to have to buy a seperate product to work with CF and use DW CC to do my layout work. If support for CF doesn't get put back into then I will be dropping CC all together and moving to alternative options such as Gimp and Eclipse. VERY disappointed long time customer!