VSS6.0d to VSS 2005 migration
Are there any known issues for,
- VSS6.0d to VSS 2005 migration?
- Using VSS 2005 with VB 6?
Also, how do we migrate VSS6.0 database to VSS 2005 database?
Thanks,
Are there any known issues for,
Also, how do we migrate VSS6.0 database to VSS 2005 database?
Thanks,
This thread has info on using VSS2005 with VB6.
Thanks Richard!
I integrated the VB 6 with VSS 2005, everything looks good except one minor issue. I don't see the red checkmark against the checked-out file. I am not sure whether it’s something specific to my installation or it’s a known problem. To reproduce the behavior Pease follow these steps,
When you re-open the project, is there a Refresh Status button you could click to refresh the glyphs? Other than that, I am not sure why the checkmark is missing. You could log a bug if you want to http://lab.msdn.microsoft.com/productfeedback/default.aspx.
Also, did you try to check in the file and then check out the file to see if the checkmark appears for checked out files?
Hi,
I am part of a developers group and we have been using VSS6.0d for more than a year now. I am evaluating changing to VSS2005. I understand we will have to uninstall VSS6.0d and install VSS2005 on the server and workstations. Before I go ahead with this, I will like to know how other users are doing with VSS2005. I am very satisfied with VSS6.0d, with its integration wih VB6.0 and VS2003, and will like to know if the experience with VSS2005 will be similar or better.
Thanks,
Angel
As I'm researching ongoing corruption issues in a VSS6 database currently and stumbled across your comment I thought I might try to save you some grief.
There is a bug in the VSS 2005 client that is tied to PDF file corruption. There are two knowledge bases about it at http://support.microsoft.com/kb/925234 and http://support.microsoft.com/kb/923434. However, these KBs make the problem sound isolated to only PDF files and we're having corruption issues that we haven't ever had in the past AFTER creating a PDF archive and experiencing the file corruption mentioned in the KBs above.
I recommend to you what I just recommended to our team here: revert to the VSS6 client indefinitely. I frankly don't see enough bells and whistles in the 2005 client to justify risking database corruption.
Over the last 15+ years I have been a software developer I have learned to (1) Keep It Simple, Stupid and (2) If it works, don't "fix" it.
Peace!
Mike, thanks for the Input. I am interested in the VSS2005 mainly because of the option for Internet Access, which VSS6.0d does not have. I have some developers that work on a remote office, and I want them to use VSS. What I will possibly do is set up a VPN in order for them to access VSS6.0d. In another forum Alin Constantin (www.alinconstantin.net) told me of some third party options for VSS6.0d Internet Access. Do you use Internet Access with VSS6.0d, and if so, how did you set it up ?
Thanks again,
Angel