Dreamweaver CS3 plugin?

Beth · Post by **Beth** » Wed Nov 14, 2007 1:29 pm

Also, did you create a "site?" You will either have to create a new one or edit the one you have and you want to put Vault in as how you connect to a server.

garbri · Post by **garbri** » Wed Nov 14, 2007 5:11 pm

The Vault_DWIDE.dll is located in both C:\Program Files\SourceGear\Vault Client and C:\Program Files\Common Files\Macromedia\8\SourceControl. The version of this file in both cases is 4.0.4.15848.

The HKLM\SOFTWARE\SourceGear\Vault Client has these keys:
* InstallDir is C:\Program Files\SourceGear\Vault Client.
* SCCServerName is SourceGear Vault VS2003 Compatible Client.
* SCCServerPath is C:\Program Files\SourceGear\Vault Client\VS2003_Client\VaultIDE.dll.

Also, we did an upgrade from Vault 3.1. Could this have affected anything?

garbri · Post by **garbri** » Wed Nov 14, 2007 5:15 pm

Tried both adding a new site and modifying the properties of an existing one. In both cases, the remote access options list a range of items including Microsoft SourceSafe but not SourceGear vault.

Regarding my previous post where we attempted to include 'missing' DLLs, that runtime error would appear when the properties page for a new site was being displayed. This would appear to suggest that when those DLLs are not present, DreamWeaver does not make any headway in bringing up the SourceSafe option. When the DLLs are present, we have included the wrong ones which cause a runtime error. Is it possibly to do with a certain installation 'extra' which was not installed, therefore resulting in missing DLLs?

Beth · Post by **Beth** » Thu Nov 15, 2007 11:13 am

You've verified that the Vault client is working separately, correct?

The only .dll that should need to have anything done is VAULT_DWIDE.dll with copying it to the location I mentioned, and that only needs to be done if Vault didn't do it.

Is it possible for you to uninstall your Vault client, perform a repair install on Dreamweaver, check that all your Dreamweaver projects look ok and work, then install Vault again? After installing Vault, then create a new site.

garbri · Post by **garbri** » Thu Nov 15, 2007 4:33 pm

We use vault daily for source control of our Visual Studio 2003 projects and have not experienced any problems with the client.

The Vault_DWIDE.dll file was installed by Vault into both its client directory and the Macromedia 'common' directory and we have not modified it.

As far as a reinstall goes, I don't think it can be done soon as the developers may not wish to risk a working environment. Unfortunately it looks as though we'll have to give Dreamweaver with Vault a miss until the next release.

Beth · Post by **Beth** » Fri Nov 16, 2007 4:11 pm

When you are ready, how about we connect offline? You can send me an email at support at sourcegear.com (attn: Beth) with a link to this thread at that time.

Beth · Post by **Beth** » Fri Nov 16, 2007 5:07 pm

I have another idea. I've attached the 3.5.3 Vault_DWIDE.dll if you wish to try that one. Just overwrite your other one's with it. If you don't like that idea, we can just wait until it's convenient for you while we continue looking into this.

garbri · Post by **garbri** » Sun Nov 18, 2007 4:34 pm

Hi Beth,
Thankyou for your offer to continue this offline.
However, your submitted DLL appears to work correctly. We copied it into the Program Files\Common Files\Macromedia\8\SourceControl directory only (after backing up our original file). No other DLLs which we worked on earlier were in the folder. SourceGear Vault now appears as an option in the list which is fantastic! So far we have only confirmed that checking in/out/difference operations worked but it all seems fine.
Thankyou very much for your support. My coworker and I do appreciate your time and help.

Gareth

Beth · Post by **Beth** » Mon Nov 19, 2007 9:53 am

Thanks for the follow up. The developers are working on making some changes to the 4.x plug-in with Dreamweaver. We'll get some fixes in one of the releases. Until then, any of the 4.x customers can feel free to use the 3.5.x .dll I posted.

APHA · Post by **APHA** » Wed Nov 21, 2007 9:35 am

Thanks for the DLL it worked for us as well

Chad