You should not use .NET 2.0?

[mlippert]

Just thought I'd ask for an explicit clarification.

This restriction only applies to the VaultService machine, correct?

If we're doing development and testing against .NET 2.0, that won't adversely affect the Vault Client which by necessity will live on that same machine.

Mike

[jclausius]

While we haven't done any significant testing, it seems the Vault Client has some areas which do not seem to operate correctly on .Net 2.0 Framework.

[jclausius]

I'd like to make a quick clarification. You "should" be able to use the Vault GUI client ( but not the Vault IDE client w/ VS 2005 CTP ), by modyfing VaultGUIClient.exe.config.

I did some "minor" testing on a machine w/ nothing but .Net 1.1, .Net 2.0 and VS 2005 CTP. In the limited testing I did, things seemed to work in the GUI client after making changes to the file:

Code: Select all

<configuration>

<startup>
  <requiredRuntime version="1.1.4322" safemode="true" />
</startup>

<runtime>
	<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1" appliesTo="v1.0.4322">
	<dependentAssembly>
		<assemblyIdentity name="System" publicKeyToken="b77a5c561934e089" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Data" publicKeyToken="b77a5c561934e089" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Drawing.Design" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Drawing" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Management" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Security" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Web" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Web.Services" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Windows.Forms" publicKeyToken="b77a5c561934e089" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	<dependentAssembly>
		<assemblyIdentity name="System.Xml" publicKeyToken="b77a5c561934e089" culture="neutral"/>
		<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="1.0.5000.0"/>
	</dependentAssembly>
	</assemblyBinding>
</runtime>

</configuration>

I'm providing this as a courtesy to users, so please use at your own risk.

[dan]

As a follow up to Jeff's comments, we've done limited testing, and certain things don't work at all, like the set working folder browse button. We do plan to have this all working in the 3.1 timeframe.

For those brave users who want to try this, don't be afraid to send us bug reports about it - we want to make sure we catch everything.

[mlippert]

Thanks,
I checked with some of our developers. This is definitely going to be an issue for us at some time, as we are developing a .net application, and will want to get it working with the 2.0 framework. We're not at that point yet, but by the end of January or end of February we probably will be (is that close to the 3.1 timeframe?).

Jeff, is the change to the config file just the startup element specifying the 1.1 runtime?

Thanks,
Mike

[jclausius]

Mike:

When I did my testing, I placed the entire section ( both runtime & startup ) in <configuration> section.

[mlippert]

Thanks Jeff.
I recommended that we switch to Vault from SourceSafe, and we'll be transitioning over at the end of January. I'm hoping I won't need to do this, but it's nice to know a possible solution exists.

Mike

[Perry]

FYI:

I'm happily using the Vault Client (3.0.1, and previously 3.0.0) on a machine with VS 2005 beta (8.0.40903-1900).

I looked at the IDE integration, and it didn't seem to work, and I didn't pursue it.

However, using the Vault GUI standalone client in concert with a VS 2005 project seems to be going very nicely.