"Unspecified error" in VS .NET 2003 with Merant Version Manager SCCP

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Michael Rayman (mdrayman_at_ieee.org)
Date: 08/23/04


Date: 23 Aug 2004 16:30:03 -0700

Hello,

First some background:
I am migrating many software projects from INTERSOLV's old PVCS
version control software v6.0 to Serena's Merant Version Manager v8.0.
 After the conversion of the projects, I have been opening up the
solutions in MS Visual Studio .NET 2003 to make sure that all of the
source control bindings and settings are correct so that "Get", "Check
out", and "Check In" operations will all work properly. All of these
projects were being maintained in PVCS v6.0 using MS VS .NET 2003,
just for your information.

The Problem:
The problem I'm seeing is only with some of the projects that I have
migrated to the new version of the source control software, but never
with other projects. When I open up the solution in MS VS .NET 2003
there are some errors and dialog boxes that need to be navigated in
order to change the source control bindings to point to the new source
control software project database. Now, in the normal IDE window, I
chose File => Source Control => Change Source Control... In this
dialog box, I use the "Browse" button to reconnect the .SLN file to
the actual source control project. After clicking OK, I close the
solution and cancel any "Check In" attempts. When I re-open some of
these solutions, they work OK in that I see a "Get" dialog box pop up
offering me to get the latest versions of the project files. When
opening the solutions that have problems, every one of them DO NOT
have the "Get" dialog box pop up, but rather present me with a very
useless dialog box that simply states "Unspecified error". That's all
it says. This happens with certain projects everytime I open their
solutions and this NEVER happens with other projects that always have
the "Get" dialog box pop up upon opening the solution.

I have researched this problem of the "Unspecified error" and I know
it has to do with the source control interface somehow, but nothing in
the Internet News Groups that I could find has helped me at all. If
anyone out there could offer me some help to solve this problem, it
would be greatly appreciated. I can provide much more detailed
descriptions of my actions if necessary upon request. I just wanted
to keep it somewhat brief at first.

Thank you all in advance for your help.'

Michael D. Rayman
Keithley Instruments, Inc.
mdrayman@ieee.org



Relevant Pages

  • Re: Development environment best practices?
    ... WINCEROOT tree brought over from source control, ... we've found it necessary to tweak the BSP as development progresses. ... Sounds like we can avoid this though, because the SDK only presents ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Related field Data Population Failed in Access 2003
    ... > CONTROL? ... >> source control = Products, ... >> 2) Say, I find out the second query, how do I reference the selected company ...
    (microsoft.public.access.modulesdaovba)
  • Re: Visual Basic 2008 Express "Exclude From Project" ...
    ... Get a source control repository and this is not a big issue. ... single solution to work on these files since creating identical ...
    (microsoft.public.dotnet.languages.vb)
  • RE: VS.NET 2003 dont recognize Source Safe controled files
    ... control. ... rebound correctly (the bound folder is logically "moved" to include those ... Use File/Source Control/Change source control dialog. ... I suspect you have the win32 folder bound to something like ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Version Control Sofwtare
    ... Will I benefit by actually using Version control Software? ... Any lone developers using software for Version control? ... I spent the longest time evaluating different VCS systems and found them all to be a chore to use - and as it usually goes, if something is a pain to use, you will end up not using it as properly and as much as you should - until i found one that i was really happy with an actually enjoyed working with. ...
    (borland.public.delphi.non-technical)