Sourcegear checking in/out

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Bill Nguyen
    #1

    Sourcegear checking in/out

    I've just installed Sourcegear vault for a single user.
    I was able to add a VS05 project to the repository. When I checked out on
    the same machine, It worked well. When I checked out from a different
    machine, I always got the error "The application for project <project path
    name.VBPROJ> is not installed. Make sure the application for project type
    (.vbproj) is installed"

    This is the same error as if I just simply copy the folder from 1 machine to
    another. Is Vault working with VS 2005 at all?

    Thanks

    Bill


    Tags: None
    • Don
      #2
      Re: Sourcegear checking in/out

      I had the exact same error yesterday, but it had nothing to do with
      Sourcegear Vault (which I also use). This error, for me, was caused because
      I did not have the correct .NET framework installed on a machine (installed
      1.0 instead of 1.1, oops).

      Check to make sure you have the right version of the .NET framework
      installed on the different machine.

      - Don


      "Bill Nguyen" <billn_nospam_p lease@jaco.com> wrote in message
      news:OPbx7IGdGH A.4108@TK2MSFTN GP03.phx.gbl...[color=blue]
      > I've just installed Sourcegear vault for a single user.
      > I was able to add a VS05 project to the repository. When I checked out on
      > the same machine, It worked well. When I checked out from a different
      > machine, I always got the error "The application for project <project path
      > name.VBPROJ> is not installed. Make sure the application for project type
      > (.vbproj) is installed"
      >
      > This is the same error as if I just simply copy the folder from 1 machine
      > to another. Is Vault working with VS 2005 at all?
      >
      > Thanks
      >
      > Bill
      >
      >[/color]


        Comment

        • Bill Nguyen
          #3
          Re: Sourcegear checking in/out

          Don;

          I have .NET framework 1.1 and 2.0 installed on both machine. This was done
          automatically with the installation of VS2005 on each machine. The only
          different is that the "different" machine also has VS2003.
          Bill

          "Don" <unknown@oblivi on.com> wrote in message
          news:Ers8g.1470 15$WI1.8828@pd7 tw2no...[color=blue]
          >I had the exact same error yesterday, but it had nothing to do with
          >Sourcegear Vault (which I also use). This error, for me, was caused
          >because I did not have the correct .NET framework installed on a machine
          >(installed 1.0 instead of 1.1, oops).
          >
          > Check to make sure you have the right version of the .NET framework
          > installed on the different machine.
          >
          > - Don
          >
          >
          > "Bill Nguyen" <billn_nospam_p lease@jaco.com> wrote in message
          > news:OPbx7IGdGH A.4108@TK2MSFTN GP03.phx.gbl...[color=green]
          >> I've just installed Sourcegear vault for a single user.
          >> I was able to add a VS05 project to the repository. When I checked out on
          >> the same machine, It worked well. When I checked out from a different
          >> machine, I always got the error "The application for project <project
          >> path name.VBPROJ> is not installed. Make sure the application for project
          >> type (.vbproj) is installed"
          >>
          >> This is the same error as if I just simply copy the folder from 1 machine
          >> to another. Is Vault working with VS 2005 at all?
          >>
          >> Thanks
          >>
          >> Bill
          >>
          >>[/color]
          >
          >[/color]


            Comment

            • Don
              #4
              Re: Sourcegear checking in/out

              The fact that you say this:

              "This is the same error as if I just simply copy the folder from 1 machine
              to another."

              Makes it sound like it's not a SourceGear Vault problem.

              You might want to try uninstalling the frameworks and reinstalling them.
              Maybe the order in which they were done screwed something up? Or maybe
              VS2003 is trying to open up the project instead of VS2005 on that machine?
              In that case, maybe repairing the VS2005 install might help?

              - Don


              "Bill Nguyen" <billn_nospam_p lease@jaco.com> wrote in message
              news:%23oFyFjHd GHA.3348@TK2MSF TNGP03.phx.gbl. ..[color=blue]
              > Don;
              >
              > I have .NET framework 1.1 and 2.0 installed on both machine. This was
              > done automatically with the installation of VS2005 on each machine. The
              > only different is that the "different" machine also has VS2003.
              > Bill
              >
              > "Don" <unknown@oblivi on.com> wrote in message
              > news:Ers8g.1470 15$WI1.8828@pd7 tw2no...[color=green]
              >>I had the exact same error yesterday, but it had nothing to do with
              >>Sourcegear Vault (which I also use). This error, for me, was caused
              >>because I did not have the correct .NET framework installed on a machine
              >>(installed 1.0 instead of 1.1, oops).
              >>
              >> Check to make sure you have the right version of the .NET framework
              >> installed on the different machine.
              >>
              >> - Don
              >>
              >>
              >> "Bill Nguyen" <billn_nospam_p lease@jaco.com> wrote in message
              >> news:OPbx7IGdGH A.4108@TK2MSFTN GP03.phx.gbl...[color=darkred]
              >>> I've just installed Sourcegear vault for a single user.
              >>> I was able to add a VS05 project to the repository. When I checked out
              >>> on the same machine, It worked well. When I checked out from a different
              >>> machine, I always got the error "The application for project <project
              >>> path name.VBPROJ> is not installed. Make sure the application for
              >>> project type (.vbproj) is installed"
              >>>
              >>> This is the same error as if I just simply copy the folder from 1
              >>> machine to another. Is Vault working with VS 2005 at all?
              >>>
              >>> Thanks
              >>>
              >>> Bill
              >>>
              >>>[/color]
              >>
              >>[/color]
              >
              >[/color]


                Comment

                Previous template Next
                Working...