Forum Discussion
swapnildaphal
15 years agoOccasional Contributor
Hi Alex,
Thanks for the suggestion but I would like elaborate my doubt further
What I require is TestExecute licens holder should not be allowed to open .scs files.But this user have all Testcomplete projects present locally on his machine for execution purpose and so can access scs files easily.
We dont want to expose some important key utility files.
We are using VSTS for managing our code base, we have put check in /check out restrictions to desired user but this provides restriction on check in/out level and I am thinking about making my .SCS files private.
Currently I am trying to understand and use "Connected Application " concept suggested by Jared.
Regards,
Swapnil
Thanks for the suggestion but I would like elaborate my doubt further
What I require is TestExecute licens holder should not be allowed to open .scs files.But this user have all Testcomplete projects present locally on his machine for execution purpose and so can access scs files easily.
We dont want to expose some important key utility files.
We are using VSTS for managing our code base, we have put check in /check out restrictions to desired user but this provides restriction on check in/out level and I am thinking about making my .SCS files private.
Currently I am trying to understand and use "Connected Application " concept suggested by Jared.
Regards,
Swapnil