Changes made to the project in VisualStudio are not reflected in the .abproject about icenium-cli

[ligaz]

We plan unify our project file format and settle to the JSON based one currently available in the CLI. This will allow sharing of projects between the many client tools we have right now. Here are some of the users stories that we are currently envisioning:

1. Multi-user collaboration directly using source control system
   • Requires common project-related data to be stored in common format, understandable and supported by all clients (Graphite, Mist, VSE, CLI) and to be included in the source control repository.
   • This is the most common collaboration scenario.
   • Might have technical problems with VSE, because of its MSBuild based project file format.
2. Sync VSE/CLI project with the cloud environment (single user scenario with no collaboration involved)
   • Use VSE and CLI as cloud clients and transfer changes between VSE/CLI and Graphite/Mist without need of source control repository
   • Link with cloud/open from cloud functionality
   • Simple conflict resolution mechanism (like in Graphite)
   • For team collaboration should fallback to 1
3. Platform team collaboration story with VSE/CLI (mix 1 and 2)
   • Share projects from VSE/CLI with the team transparently using Telerik Platform (of course using source-control system)
   • Relies heavily on “Link with cloud”, basic team collaboration (i.e. 1) and Platform team collaboration stories
4. Multi-user collaboration from different operating systems (Mac and Windows)
   • Involves all previously mentioned scenarios
   • Needs integration with clients for different operating systems (Mac and Windows)
   • Might be implemented like 1 or 3, depending on the team preferences

Does those make sense for you? It would be great if you could share your feedback with us and help us shape this important feature.