Microsoft KB Archive/323684

= Comments Are Limited to 512 Characters If You Add Comment from the Command Line =

Article ID: 323684

Article Last Modified on 2/22/2007

-

APPLIES TO


 * Microsoft Visual SourceSafe 6.0C

-



This article was previously published under Q323684



SYMPTOMS
If you use the command line to add a comment to a Visual SourceSafe item, Visual SourceSafe limits your comment to 512 characters. However, if you use the Visual SourceSafe user interface to add a comment, the maximum size of a comment is 4,096 characters. You can use this fix to allow 4,096 characters from the command line so that the command line is consistent with the Visual SourceSafe user interface.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

  Date         Time   Version             Size   File name --  03-Jun-2002  09:20  06.00.9601        199,952  Analyze.exe 03-Jun-2002 09:20                    295,696  Ddconv.exe 03-Jun-2002 09:20                    420,624  Ddupd.exe 03-Jun-2002 09:20                    224,969  Delta_ss.exe 03-Jun-2002 09:20                    111,888  Mkss.exe 03-Jun-2002 09:20                    231,143  Pvcs_ss.exe 03-Jun-2002 09:20                     38,790  Readmess.htm 03-Jun-2002 09:20                    397,584  Ss.exe 03-Jun-2002 09:20  06.00.9601         12,048  Ssadmin.exe 03-Jun-2002 09:20  06.00.9601        562,448  Ssapi.dll 03-Jun-2002 09:20  06.00.9601        499,472  Ssarc.exe 03-Jun-2002 09:20  06.00.9601         16,656  Ssexp.exe 03-Jun-2002 09:20  06.00.9601      1,132,304  Ssgui.dll 03-Jun-2002 09:21  06.00.9601        140,800  Ssint.exe 03-Jun-2002 09:21                    152,336  Sslogin.exe 03-Jun-2002 09:21  06.00.9601        497,424  Ssrestor.exe 03-Jun-2002 09:21  06.00.9601      1,412,368  Ssscc.dll 03-Jun-2002 09:21  06.00.9601        480,528  Ssus.dll 03-Jun-2002 09:21                    101,136  Testlock.exe 03-Jun-2002 09:21                    144,144  Unlock.exe 03-Jun-2002 09:21                    121,104  Updini.exe



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Visual Studio .NET 2003.



MORE INFORMATION
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

138298 INFO: Visual SourceSafe System Capacities and Specifications

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB323684

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.