SourceGear Support

Yes, but it fetches it via DHCP - it could potentially change. I guess we could do a reservation - or just give it a static IP - unless there's a better way? (I only ask because there's a chance we could want to do this over the net outside a vpn in future - therefore no chance of this workaround) T...

Scenario: I need to connect to a Vault server through a VPN, as well as locally. While on the VPN, the DNS name I have to use to refer to the Vault box is different from the DNS name I would use on the LAN. The problem with this is that the source control bindings to the Vault server address are sto...

Well I can report that this worked. Sort of. Vault is back up and running now (don't know what was causing the issues the first time I tried it), but every VS2005 solution stored in source control is broken - the solution opens, but all the projects are "unavailable". "Reloading"...

I will give this a go (deleting all databases apart from sgvault and sgmaster) after hours one day.

Thanks for the confirmation.

Hi there

Appreciate your work on this - where and when will the 4.1 beta availability be announced?

Cheers
Tom

While I'm here, any news on Vault/Fortress + VS2008, given that Microsoft have committed to a November release?

Vault not being available for VS2008 is a blocking issue for us - either we don't use VS2008 or we don't use Vault.

Thanks.

Hi I've been evaluating Fortress, but we have chosen to just go with Vault for source control instead of using the whole ALM solution in Fortress. I need to basically convert a Fortress installation into a Vault installation so I can apply Vault-only licenses to it. I can't find any documentation on...

And in Fortress? (1.0.4 exhibits this)

+1 for this to be fixed.

Then I shall shut up and very much look forward to a preview build

We're also paying customers - and while yes Microsoft *can* change APIs on a moments notice, it's unlikely that they would in this case in my opinion. If SG put out a preview in the next few weeks that was labelled compatible with VS2008 beta 2, then we wouldn't be yelling at them when beta 3 / rele...

I honestly can't believe I'm the first person to ask this question, given what a huge release it is.

It's not the like VS2008 hasn't been available for preview for a long time...

Well yes, exactly - without Fortress under VS2008 we effectively can't start coding .NET 3.5 projects making use of the new language features like LINQ - despite them being pretty mature and released with this "go-live" license.

Tends to pull me away from using Sourcegear, if I'm honest.

Is there no way whatsoever you're going to make this functionality available, even on a pre-release basis, for this VS2008 beta, even though it's been released with a "go-live" license?

Hi

What's the status of compatibility of Fortress with the new VS2008 beta 2?

I only see the VS2003-compatible client in the Current source control plug-in drop down list in Options->Source Control in VS2008.

Thanks
Tom