Author Topic: Version control not always available  (Read 2794 times)


  • Junior Community Member
  • Posts: 2
  • Hero Points: 0
Version control not always available
« on: July 24, 2009, 03:41:55 pm »
I just upgraded from SE2007 and wonder if there is a better way to handle the following problem:

I use the clearcase SCC provider and have a workspace connected to it.  Slickedit is setup to restore the last open workspace when it is opened.

When I am away from the corporate network and try to open slickedit, it just hangs up.

In SE2007, I needed to set up a separate slickedit configuration directory and create a shortcut to invoke slickedit with the -sc option pointing to my second configuration.  Then, I needed to create a separate workspace for use when disconnected that does not try to connect to clearcase.

Is this still the best way to proceed? ???

ScottW, VP of Dev

  • Senior Community Member
  • Posts: 1471
  • Hero Points: 64
Re: Version control not always available
« Reply #1 on: July 27, 2009, 02:46:35 pm »
Are your workspace and project files (.vpw and .vpj) stored in the VOB? If so, then I think you will need to use a separate config for when you are not attached to Clearcase, as you have already suggested. Since you aren't connected to Clearcase, you wouldn't be working on the same set of files, so creating a different workspace for that seems like the right thing to do. You can put a shortcut icon on your desktop for each different config.

If your workspace and project files are stored locally, which is something we highly recommend, then you may be able to avoid this by changing the Auto Restore settings. Select Tools > Options > Application Options > Auto Restore and change the following to "False": Auto restore files, Auto restore, workspace files, Auto restore working directory.