Using Visual Source Safe and EA

[JeffCarlson]

I've been using this product for over 6 months and I like a lot of things about it.  I also there is a lot more to learn.  When we started using EA we had dead lines so we didn't worry about integrating EA with VSS.  We have all of our major products behind us and we are starting to refactor and make enhancements.  All of our code is in VSS and we use Visual Studio as our IDE.  I've associated my model with the project in source safe that the model is for and set the directory to the working directory for VSS on the PC.  What does this buy us, if we make changes, EA doesn't check out the class so we can generate the class to include our changes.  Ifind that I have to go to VSS or the IDE and check out the class, go to EA and generate and then go back to VSS or the IDE and check it back in.  There should be an easier way at least I hope there is and it is just my inexperience with the product that is causing my extra work.  I would think that if you have VSS enabled in EA, it should ask you to check out and give you the ability to check it back in.  

If this is already possible, please let me know how to do it, the help wasn't really helpful on this subject.  Also if it is not possible, when might it be.

Thanks,
Jeff Carlson

[JourneymanDave]

Jeff, I noticed a day or two ago that there's a new product/enhancement being developed to more closely link EA and Visual Studio .Net.  If you're a registered EA user, check out the link for registered users from the EA home page, and locate the announcement for the MDG (model driven generator) link for Visual Studio .Net.

I browsed the feature set and downloaded the beta myself, but I haven't loaded it and tried it out yet.  Looks like it may at least partially resolve your (reasonable) issues in using EA with VS .Net.

There's no pricing or licensing information available, but assuming that the MDG Link does what I think I understand from reading the feature set, I'll seriously consider investing in it.  I'm already running Borland's Together for VS .Net and it's pretty nice for the design model/code cycle.  It just isn't as comprehensive as EA, which would be more to my liking.