By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,962 Members | 1,889 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,962 IT Pros & Developers. It's quick & easy.

Problems with Visual Source Safe and Dreamweaver

P: n/a
dear dreamweavers,

we use Dreamweaver MX 6.1 and have following "BIG" problem.

I create a new file with dreamweaver and check it in into VSS.
Another user creates a file with the same name, same folder on his computer
an check it into VSS too.

VSS or dreamweaver overrides my file with the file of the second user!!!
that means that in the VSS history of the file there are 2 versions!

well all my work on the file is gone!!!
are we doing something wrong or is there a problem with dreamweaver and vss?
please tell me if you have the same problem... and if possible the way to
solve it

greetings
patrick merhi
university of technology aachen, germany
Jul 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
In article <bp**********@nets3.rz.RWTH-Aachen.DE>, pa*****@merhi.de
says...
dear dreamweavers,

we use Dreamweaver MX 6.1 and have following "BIG" problem.

I create a new file with dreamweaver and check it in into VSS.
Another user creates a file with the same name, same folder on his computer
an check it into VSS too.

VSS or dreamweaver overrides my file with the file of the second user!!!
that means that in the VSS history of the file there are 2 versions!

well all my work on the file is gone!!!
are we doing something wrong or is there a problem with dreamweaver and vss?
please tell me if you have the same problem... and if possible the way to
solve it


It's unlikely to be a JavaScript issue. Common sense tells me that you
should try a VSS group.

--
Hywel I do not eat quiche
http://hyweljenkins.co.uk/
http://hyweljenkins.co.uk/mfaq.php
Jul 20 '05 #2

P: n/a
On Mon, 17 Nov 2003 18:02:21 -0000, Hywel Jenkins
<hy**********@hotmail.com> wrote:
It's unlikely to be a JavaScript issue. Common sense tells me that you
should try a VSS group.


Then quickly chuck it away, and get a proper version control system
that allows concurrent editing... cvs would be the obvious if possibly
not best choice.

Jim.
--
comp.lang.javascript FAQ - http://jibbering.com/faq/

Jul 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.