Skip to main content
I
IM The Web Guy
Participant
June 19, 2013
Answered

No ASP/ASP.Net support in Dreamweaver CC

  • June 19, 2013
  • 13 replies
  • 93099 views

Another Disabled or depreicated 'feature'. No ASP of ASP.Net support in DW CC.

At: * Vista/Windows 7: C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC\Configuration\DisabledFeatures there are a some .mxp files to add these functions back.

Took the  steps required to convert mpx to ZXP.

http://www.projectseven.com/products/cloud-install.htm

The extension, ASP_JS_Support.mxp, once converted throws an error. It is searching for files in directories that do not exist. There is  Menus.xml file in the /configuration/Menus/ directory, the the 'element' is not in the file at all. See image below.

This is my most required function.


When we open a new file, many file type starter pages are no longer available including ASP, Cold Fusion etc. Are these going to be added back?

Add my voice to legions of others showing Our disappointment with DW CC's lack of support for developers. CC is simply a CSS, HTML WYSYWIG editor now. We should not have to load extensions to the primary program we use to develop our websites. While HTML 5 and CSS can develop great sites, the fact is there are millions of websites that function perfectly without these and will continue to do so.

IMHO Adobe focused completely on new technology, which is not even supported fully by browsers, and ignored technologies that are in use today. You missed by a mile and I regret purchasing a Cloud Account just to see what a drop shadow or curved border looks like in live view.

Support? Do I even need to go there?

I had such hopes for this version of DW, looks like CS6 will remain my main program.

    This topic has been closed for replies.
    Correct answer RobertoSonzogni

    I solved this adding ".asp" to the "open in dreamweaver" in the preferences, but also configuring the site server model as "asp vbscript".

    13 replies

    Show previous replies
    karindpowell
    karindpowell
    Participating Frequently
    June 25, 2013

    I'm looking at Microsoft® WebMatrix 3 http://www.microsoft.com/web/webmatrix/ --- very interesting! See also video "Introduction to WebMatrix" on PluralSight.com

    I'm keeping Dreamweaver CC for all it's other features, but I think I'm going to have to use WebMatrix a little bit for some of the features it has that Dreamweaver CC does not have.

    If I end up uninstalling it, well... I'm back in the same boat.

    Here are three images of Creating A New File in WebMatrix 3. (sorry Adobe, but you forced our hand!)

    S
    ShineCC
    Participant
    October 10, 2013

    Thank you for the link to Microsoft® WebMatrix 3! I just need to edit one tiny part of a website for a client. I'm not a webmaster or even close but I can do what is needed if it's simple. Hopefully I will be able to use WebMatrix 3 to change just a couple of words on their website.

    Add me to the many folks who can't believe that Adobe has decided what direction our website development will go. There is still the support of the legacy websites that will be slowly updated. Businesses don't move quickly on changes so it might be a long time. Having to use more than one tool when your product used to do it all is short-sighted. Many people will try the other options and just might find that they like the other products better.

    A
    Anonymous
    June 23, 2013

    I just noticed this problem in the trial Dreamweaver CC too.  Will be uninstalling tomorrow and stick with CS6 and Expression Web Designer. Not supporting ASP & ASP.NET is a deal breaker. I don't think I'm even going to bother learning what else is new in Dreamweaver CC. *sigh*

      B
      Community Expert
      Ben MCommunity Expert
      Community Expert
      June 23, 2013

      I'm not sure why Adobe deleted the linked archive of deprecated features over time found here ( http://helpx.adobe.com/dreamweaver/kb/deprecated-features-dreamweaver.html ), the closest article they have left is here ( http://kb2.adobe.com/community/publishing/923/cpsid_92324.html ).

      Regardless, ASP.NET support was deprecated back at CS4.  If you added a number to CC this would be CS7.  So we have been since 2008 with no support for ASP.NET.  Classic ASP was technically supported, although there were many articles posted about the server behaviors being out of date, on both ASP and PHP sides, which caused Adobe to listen to the masses and discontinue legacy support for that if they were not going to be updated because I think we can all agree it would be better to remove something that could potentially open up security holes across the web then to leave it in for legacy's sake.

      While Preran speaks for Adobe and gives the official answer, many within the community believe the reason why support was removed goes back to the reasoning of why Adobe bought Macromedia.  Reason being that they cannot develop products around a proprietary technology, in this case Microsoft's, without their development lagging behind.  And the other part of the reason was the numbers game.  Based on 2 recent surveys ( http://news.netcraft.com/archives/category/web-server-survey/ , http://w3techs.com ) only 20% of servers run ASP/.NET.

      Since that decision was made in 2008 to discontinue .NET support, I would typically recommend that someone invested in ASP technologies to use what was Frontpage, and then Expression Web and now Visual Studio Web Designer ( http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products ).  There's not really much else I can recommend that comes to mind.

      Preran
      Community Manager
      PreranCommunity Manager
      Community Manager
      June 23, 2013

      Hi SnakEyez02, all

      Thank you.  It's true that Dreamweaver is moving towards standards-based web technologies. As I said previously, we are collecting all feedback, and will be sharing our roadmap with everyone very soon covering how we will be prioritizing our work based on various inputs from our users. The idea is to evolve Dreamweaver into the kind of software that will meet the demands of current and future web standards while still remaining light on its feet.

      We are still providing Dreamweaver CS6 for some time to ensure that we don't leave those users behind who are working with technologies where we are limiting our focus. And as you know already, you can run Dreamweaver CS6 and CC in parallel which means you will always have a choice of working with the latest features while maintaining your current workflows.

      About the broken links, apologies in advance. The policy is to unpublish documents that have ceased to be popular or cannibalizing the popularity of our latest, updated documents. Having said that, I will check with the team about the reason why these links don't work any more.

      Our presence on various social platforms and on the pre-release forum is testimony to the fact that we are hearing every one very seriously. Instead of multiple posts that will confuse everyone, we want to complete the process of listening before we publish a comprehensive reply.

      Thanks,

      Preran

      Preran
      Community Manager
      PreranCommunity Manager
      Community Manager
      June 19, 2013

      Hi Web Guy,

      Can you check out this discussion and let us know if you still need help?

      http://forums.adobe.com/thread/1236373?tstart=0

      Thanks,

      Preran

      I
      IM The Web GuyAuthor
      Participant
      June 19, 2013

      That post has nothing to do with the issue I am speaking of here. I have no problem with file associations within windows. My post talks about the lack of support within the program itself.

      karindpowell
      karindpowell
      Participating Frequently
      June 20, 2013

      Emerging technologies - what about the hundreds of sites I have built with tried and true technologies still in production. If HTML5 and CSS are the only focus of DW CC then I have wasted my money signing up for Creative Cloud simply for a robust editor, only so I can go back to DW CS6 to get the real work done. What can HTML5 and CSS do with a recordset? If PHP is not used, the DW CC is worthless.

      I cannot believe there was a consious decision to depreciate technologies currently in production. I am very dissapointed in DW CC's lack of support.

      I have wasted enough time on this, I think it's refund time. If I can ever get ahold of support.


      IM The Web Guy -- You speak for many, myself included. The organization for which I do much of my work is sticking with its legacy applications and NOT planning on changing all of them overnight simply because Adobe decides that the future is here. Naturally, they may do so slowly or with newer applications, but SHAME on Adobe for not considering this! Not every client is in a hurry to spend tons of money on re-coding -- especially those with limited funds. [shocked] and [sad].

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices