Version Control Walkthrough

[jnapier]

The documentation on Version Control is completely weak.  If you try to follow what is in the documentation, you will be left trying to pull your hair out.  I'm evaluating this product for purchase and it seems like there are alot of good features, but without spending a whole week trying to figure out how to use the product, I will never know if the features work or not.

Can somebody please walk me through setting up version control.  From start to finish please.  If you look at the documentation under "Using Version Control", you will see that the "Submit a package to Version Control" topic is wrong.   I never get prompted to enter an "XML Filename".

Please help so I don't have to throw this product to the junk heap.  Are there any other customers out there that have some feedback on this product?

Thanks,
Jesse

[mbc]

The first step is to take a looong breath and relax
Generally people in here like EA, and generally we are very helpful when we know how to do something. However, a positive attitude works better than threats to throw the product away. After all, we (your fellow users) gain or lose nothing whether you buy it or not.

Best regards
Mikkel

[jnapier]

I was being sarcastic.

I guess if the documentation was any good then I wouldn't have to be sarcastic.  

[mbc]

If you want to bitch about the product, write to Sparx Systems, not to us, the users. But if you took some time to get acquainted with the amazing level of support and helpfulness you get from Sparx, you will find that they don't deserve it either.

Mikkel