Extension Manager CS5 on Windows 7
Thank you for your reply. Following is the question I submitted as "#3". The number is in the upper right hand corner of the request field.
"I am having a somewhat similar situation with Dreamweaver CS5 and Extension Manager 5.0 on Windows 7. DW will not open Extension Manager from within the program i.e. Commands > Manage Extensions. I can open Extension Manager through the start menu. Then when I double click on a WA extension (cannot access a WA extension through EM, Install Extension in EM is grayed out) EM starts to install but stops and gives the error, "This extension cannot be installed, it requires Dreamweaver version 8 or greater".
Have tried "Run as Administrator" per Adobe Forums on both DW and EM.
I do have a CS4 version of EM installed, do you think DW could be using this version of EM as the "default appication for mxp files"? Should I try uninstalling EM CS4?"
If I am following correctly I think your suggestion for "the crux of the issue that you are having is that the install button is not available in the extension manager, therefor, you cannot use the extension manager to install new extensions" is "the first thing I would try is to delete the Dreamweaver Configuration folder. See the Common installation issues pdf for details on locating the configuration folder:
technote...ion_issues.pdf In the same location you find the DreamweaverCS5 folder, there will be a Extension Manager CS5 folder as well, delete the configuration folder under that path also, this should hopefully correct the issue with the Install button in the extension manager being greyed out."
I could not delete the DW Configuration folder and am a little reluctant to do so as it looks like it contains far too many important folders and am not sure it would rebuild and I might have to reinstall DW CS5. Not that this would be too hard to do but would not look forward to reinstalling the SiteCache.
I was able to delete WinFileCache-530B2A19.dat as well as the DW Extension Manager CS5 Configuration folder - both to no avail.
I do not think you are lazy, you reply promtply and at least try to provide solutions. I am trying to find a better way to get Adobe's attention and I will take your suggestions to heart.
By the time this issue is resolved Adobe will be forcing us to upgrade to another version (I understand CS6 is in the works) and perhaps this issue will be resolved but I fear there will always be a new issue.