Forum Discussion
dkinne
11 years agoOccasional Contributor
I know about excluding the .bak from the source control.
In my case I think it's a little bit more complicated to explain.
to my second point of disabling to create the .bak from the cloned project:
1. I run several vm-ware player 9 machines at my host. In every VM is TestComplete 9.31 installed
2. Amongst other things we develop plug-ins for XML-Editors like XMetal, Arbortext and so on. That's why i've used an USB-Stick locally and create a Share on it. From every VM I connect to the Share at my host open open the TC Project over the Share.
3. Only me is working over the Windows Share and we have only 1 Floating TC Lic, so that the Test-Project can only opend once
4. The Test-Project is organized as an Project Suite with several Projects which includes many Keyword-Tests with Units and so on
5. The Issue occurs only then, when trying to save an change within the Scripts Folder of one special project (which was cloned before) and only if I working over the windows share.
6. All other Projects within the Projects Suite had no Problems, when changing Code there inside the scripts area.
The easiest why to fix would be to exclude the .bak creating withtin TestComplete. But when this is not configurable via any option then the goal would be to copy the files over the network locally to the virtual machine directly or use our svn and check-out check-in every time when using a different VM the files from the trunc. This is annoying, because of struggling with so many VM's. The Setup with the windows share was technical ugly, but quick and nice for my setup.
Regards,
Dirk
In my case I think it's a little bit more complicated to explain.
to my second point of disabling to create the .bak from the cloned project:
1. I run several vm-ware player 9 machines at my host. In every VM is TestComplete 9.31 installed
2. Amongst other things we develop plug-ins for XML-Editors like XMetal, Arbortext and so on. That's why i've used an USB-Stick locally and create a Share on it. From every VM I connect to the Share at my host open open the TC Project over the Share.
3. Only me is working over the Windows Share and we have only 1 Floating TC Lic, so that the Test-Project can only opend once
4. The Test-Project is organized as an Project Suite with several Projects which includes many Keyword-Tests with Units and so on
5. The Issue occurs only then, when trying to save an change within the Scripts Folder of one special project (which was cloned before) and only if I working over the windows share.
6. All other Projects within the Projects Suite had no Problems, when changing Code there inside the scripts area.
The easiest why to fix would be to exclude the .bak creating withtin TestComplete. But when this is not configurable via any option then the goal would be to copy the files over the network locally to the virtual machine directly or use our svn and check-out check-in every time when using a different VM the files from the trunc. This is annoying, because of struggling with so many VM's. The Setup with the windows share was technical ugly, but quick and nice for my setup.
Regards,
Dirk
Related Content
- 2 months agoStoplight
Recent Discussions
- 4 hours agoSlickRick
- 5 hours agoSlickRick
Name Mapping Issue
Solved7 hours agokgreger1