Before trying this, I wanted to ask if this has been tested -- Does 2.0.6 run correctly on ASP.Net 2.0 and under VS 2005 as a client?
As an aside, how about SQL 2005 beta 2 as the DB?
I'd rather not lose another repository <VBG>
--Oren
Vault 2.0.6 on .NET 2.0
Moderator: SourceGear
The hash code issue has been addressed in 2.0.6, so you shouldn't have any repository problems.
That said, we did some light testing with 2.0.6 on .Net 2.0 Beta, and found a bunch of medium to small GUI problems that are not addressed in 2.0.6. I believe none of them are fatal, but I could be wrong. Let us know if you run into any problems for which there are no workarounds.
We haven't tested it at all on SQL 2005, so do that only for your own amusement on a test database If you do, let us know how it went though...
That said, we did some light testing with 2.0.6 on .Net 2.0 Beta, and found a bunch of medium to small GUI problems that are not addressed in 2.0.6. I believe none of them are fatal, but I could be wrong. Let us know if you run into any problems for which there are no workarounds.
We haven't tested it at all on SQL 2005, so do that only for your own amusement on a test database If you do, let us know how it went though...
-
- Posts: 47
- Joined: Tue Mar 23, 2004 3:54 pm
- Location: South Africa
- Contact:
Regarding the following comment:
and the Knowledge Base post for the release notes:dan wrote:The hash code issue has been addressed in 2.0.6, so you shouldn't have any repository problems.
What about the situation where the client has .NET Framework 1.0, 1.1sp1 and 2.0beta installed and the server only has .NET Framework 1.1sp1 installed? Are there likely to be any issues with the hash codes used?dan wrote:Client/Server Changes
Both client and server must be upgraded to take advantage of these changes:
- Both client and server are now compatible with with .Net framework 2.0 Beta
You should be fine - the compatibility required is that you should be running both the Vault 2.0.6 client and server if you have SP1 or 2.0 Beta installed. With 2.0.6, you can have any combination of .Net frameworks installed and you should be fine.CraigNicholson wrote: What about the situation where the client has .NET Framework 1.0, 1.1sp1 and 2.0 beta installed and the server only has .NET Framework 1.1sp1 installed? Are there likely to be any issues with the hash codes used?
One other thing to note however is that there are a number of bugs related to running the Vault client on the 2.0 beta framework that won't be fixed immediately, since the 2.0 framework is still in early beta. However, there will be no database problems on the 2.0 beta that we are aware of if you use 2.0.6.