DW 2017 - Code is jumping all over the place!

[ShorePatrol]

Since the update to DW 2017, I am having a horrible time with editing code in ASP pages.

Here's the issues:

1) When adding HTML code on an ASP page, there is no HTML code sense/code complete. (Or ASP code sense either)

2) The code coloring is all wrong (as I've posted in another thread)

3) The biggest problem - the code jumps to the center of the screen (the line I'm working on) when I add code to an existing line. For instance, if I have this line:

<p> </p>

and I put my cursor in the beginning tag after the P and hit space (to say, create a class like <p class="whatever">), the entire line of code jumps to the center of the screen.

I have to say, I am very unhappy with DW 2017 and thinking about rolling back. It's just too difficult to work with all these bugs.

Thanks for any help or suggestions.

[Gerry Gantt]

An additional problem with DW 2017 is that they have apparently made the source code editor a stand-alone app.  This imposes severe limits on what you can do with the code.  Moreover, you can only have ONE page open at a time and expect to do anything at all because DW essentially freezes up if you open more than one page.  I had to go back to the 2015 version to get any work done.  DW 2017 is useless for me and I am very disappointed.

[Jon Fritz · Accepted solution]

1. ASP support has been getting removed, piece by piece, over the last several versions. There is no plan currently to give any of it back that we've seen from Adobe.

2. Adobe is aware of the code coloring issues and there are ways for you to change it, however it requires changing less and json files in the program directory vs simply changing settings in the preferences area. Hopefully they've heard the outcry of frustrated users and will give some, if not all, of that functionality back

3. I'm not sure I understand what's happening there, I don't see the same effect under Windows 7.

They removed the old source code interface and replaced it with a watered-down version of Brackets. As far as I can tell, it had no effect on what one can do with the code, could you please explain what you're seeing?

As for only having one file open at a time, click the small Minimize icon in the upper right of your document window to have multiple documents open side by side, tiled or stacked as the screenshot below shows...

I also went back to CC2015 due to the html entity re-write bug explained here: Dreamweaver Help | Known issues | Dreamweaver CC 2017 this version of CC2017 is not ready for production use in my opinion.

[ShorePatrol]

Their "Known Issues" page seems to be lacking some issues...

[Jon Fritz]

Agreed. Make sure to report bugs you find, and the steps to reproduce them, here: Feature Request/Bug Report Form

The dev guys don't hang out in the forum (some Adobe employees do and will bring major issues to them directly), but they DO see the bug reports.

[ShorePatrol]

Jon - I entered a bug request...

Also, for #3 above, the code jumping only seems to happen in Classic ASP. So try opening a ".asp" page (or create one), and you should see this behavior. Driving me crazy.

And I realize they are removing Classic ASP support - but this is a little like a car dealership saying they will no longer sell you car parts, or fix your car, because your car is too old (even though there are thousands of them still driving around).

[Jon Fritz]

I hear you.

My only advice at this point would be to keep an old version of DW installed if you want to work with ASP within DW.

As a paid CC Subscriber, you have access to old versions all the way back to DWCS6 through the CC Desktop App. You can have multiple versions of the program installed on the same machine under a single license, the only limitation is that they won't run at the same time.

To get an old version through the desktop app: How to Find and Install Previous Version of Adobe Apps in CC 2015 | Adobe Customer Care Team

[Preran]

Thank you. I don't want to lay the onus on you, but if you could list out at least some of the issues that you think should be in the Known Issues doc, I will share it with the content team for their observations.

Thanks,

Preran

[ShorePatrol]

Preran,

They are listed on this page, here's a review:

1) If you open a Classic ASP page, even the HTML code sense doesn't work

2) Code Sense no longer works for ASP pages for ASP code

3) Opening an ASP page should automatically select VBScript from the lower right dropdown, but does not

4) Code coloring does not work correctly anymore

5) In an ASP page, the code "jumps" when coding (see above messages)

You can also take to your team my sentiment - I understand Classic ASP is rather old and Adobe needs to add newer technologies for things like PHP, SASS, etc - which I welcome. But removing features already part of the program, that many developers have adapted to, and become dependent on, is unnecessary and wrong. You are abandoning many developers who still need to support ASP applications, and there are many out there, and will be for years to come. Myself for example, I develop all new applications in PHP, but have 40+ classic ASP applications in a hospital setting which still need support and occasional enhancements.