One of the main design criteria was to not define or use any API so that the product would work with ANY editor, from Notepad to PowerShell Studio, from PrimalPad to the ISE and from Notepad++ to PrimalScript.īut on reading this we realized that there may be more people who are just knowledgeable enough about traditional source control systems that they may look for a means to control when something gets submitted from within an editor. The new API for Team Foundation Server is equally just overkill for VersionRecall’s target audience. The specs are pretty well hidden, change without notice and any product supporting this has to do a lot of extra work just to conform with this rather dated API. Surprised, because we intentionally did not want to use any API, especially not the Microsoft Source Control Interface. That’s a shame the automatic check-in/out in PowerShell Studio would make it all a bit simpler.” Instead, you almost want to open files by using VersionRecall’s Explorer, save them in PowerShell Studio, and then submit them to the repository back in VersionRecall. That means you can’t use the integrated check-in/out controls in PowerShell Studio. “Unfortunately, PowerShell Studio doesn’t seem to recognize VersionRecall as a source control provider (at least, it didn’t show up when I tried to configure source control in PowerShell Studio). There was one paragraph that took us a little bit by surprise: The folks over at recently published a review of VersionRecall ( )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |