We will try to answer some questions from YouTube related to the Co-operative Concept of Visual Studio video.
Question: If the code is under a source control system (for example: SVN) and you do a Checkin for a new file, then 2 Checkins of that files get generated with the changes from each user?
Answer: When you invite someone to co-operate on a code file, you’re actually working on the copy of code of who invited you, then you can check in with the changes from all users.
The source control systems today do not support the concept of co-operation, they are naturally collaborative. When working on your local copy, you’re assuming you will agree with the rest of the people with whom you had a conflict of intention, trying to make a Checkin/Commit without prior information of how they got there.
To be useful the co-operative model also requires those points of agreement (revisions), but also allows for a much lower level of granularity. To save the entire history of how you reached a solution and playback it as if you had a time machine. The good thing is that data may be used for code analysis and more accurate estimates.
Question: Users with which you share your file should be a user in SVN (or any other Source Control System)?
Answer: A user is anyone who has a co-operative version of the application and whom you can connect. You are not restricted to users who use your Source Control Management tool or other code life cycle supporting application, such as Team Foundation Server. But is should be supported in an enterprise environment. Nor do you need to have the same application, only a version compatible with beWeeVee and the file format you want to share. For example, you could share a code file so that they can edit from a web version or other text editor as long as it is able to understand the elements you are sharing.
Question: When you share, are you sharing the file or the class? Since it might be a partial class defined in two files.
Answer: Basically sharing files, folders, projects and solutions is exactly the same. In addition to sharing, the other participants should also learn about the structure of the solution, so they can understand the context for co-operation. So in the case of the partial class, you can share the multiple files or the other user may ask what it is missing.
Additionally we invite you to see the datasheet <link>. It gives you more information about possible architectures and the application domains we foresee the idea can be applied. We believe they are quite varied. We don’t rule out the possibility to see beWeeVee as the core of a version control, as it can solve some of the problems faced by existing platforms.