Messages

1

Automation Interface, Add-Ins and Tools / Re: Disconnect from version control

« on: March 17, 2011, 06:43:53 pm »

The method Package.VersionControlRemove() works for me.

I tried that. However, we're using clearcase and every then and when (when cc detects that I'm not looking at the latest version) a clearcase confirmation window (asking for checkout!) pops up needing manual intervention.

Andreas

2

Automation Interface, Add-Ins and Tools / Re: Disconnect from version control

« on: March 15, 2011, 02:19:17 am »

I'd been afraid of that.

Thanks.
Andreas

3

Automation Interface, Add-Ins and Tools / Disconnect from version control

« on: March 14, 2011, 09:48:03 pm »

Can someone please give me a hint how to accomplish the equivalent of "Disconnect from version control" (i.e. clearing the "Control Package" checkbox in the GUI) via an (e.g.) VB script? I have a nested hierarchy of packages, several of them version controlled and I'd like to export this hierarchy without the version control. Just setting the "IsControlled" attribute to "False" doesn't seem to be enough.

4

Automation Interface, Add-Ins and Tools / ImportPackageXMI() for importing a root node

« on: January 14, 2011, 09:58:19 pm »

I'm using ImportPackageXMI() for importing an XMI file. While this works well when importing beneath a package, I haven't been able to import the XMI as a root node. Is this impossible via the automation interface? The first parameter to ImportPackageXMI() is the GUID of the package to import into, which obviously doesn't exist for a root node.