DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 9 of 9

Thread: Bloody Sourcesafe!

  1. #1
    Michael Culley Guest

    Bloody Sourcesafe!

    Every time I try to check out a DLL project file whilst in a group I get the
    error message 'failed to reload project'. Does anyone know a way around
    this.

    TIA

    --
    Michael Culley
    www.vbdotcom.com





  2. #2
    Kevin Guest

    Re: Bloody Sourcesafe!


    I have the same problem, I'm sure most everyone does. I check out the project
    files and the group file from SourceSafe before loading the project up in
    VB. Not a solution but a workaround.

    Kevin

    "Michael Culley" <mike@vbdotcom.com> wrote:
    >Every time I try to check out a DLL project file whilst in a group I get

    the
    >error message 'failed to reload project'. Does anyone know a way around
    >this.
    >
    >TIA
    >
    >--
    >Michael Culley
    >www.vbdotcom.com
    >
    >
    >
    >



  3. #3
    ralph Guest

    Re: Bloody Sourcesafe!


    "Michael Culley" <mike@vbdotcom.com> wrote:
    >Every time I try to check out a DLL project file whilst in a group I get

    the
    >error message 'failed to reload project'. Does anyone know a way around
    >this.
    >
    >TIA
    >
    >--
    >Michael Culley
    >www.vbdotcom.com
    >


    Make sure your project files (*.vbp, *.vbw, *.vbg, ...) are not 'read-only'.

  4. #4
    Michael Culley Guest

    Re: Bloody Sourcesafe!

    Kevin,

    Annoying isn't it? The app I am working on is fairly large and take a while
    to load.

    BTW, we don't put the group file into sourcesafe, I think it is better not
    in there.

    ralph,

    can you give me more details. Do you mean in windows explorer? or in
    sourcesafe options?

    Thanks

    --
    Michael Culley
    www.vbdotcom.com


    "ralph" <nt_consulting32@SPAMhotmail.com> wrote in message
    news:3bfc0924$1@147.208.176.211...
    >
    > "Michael Culley" <mike@vbdotcom.com> wrote:
    > >Every time I try to check out a DLL project file whilst in a group I get

    > the
    > >error message 'failed to reload project'. Does anyone know a way around
    > >this.
    > >
    > >TIA
    > >
    > >--
    > >Michael Culley
    > >www.vbdotcom.com
    > >

    >
    > Make sure your project files (*.vbp, *.vbw, *.vbg, ...) are not

    'read-only'.



  5. #5
    ralph Guest

    Re: Bloody Sourcesafe!


    "Michael Culley" <mike@vbdotcom.com> wrote:
    >Kevin,
    >
    >Annoying isn't it? The app I am working on is fairly large and take a while
    >to load.
    >
    >BTW, we don't put the group file into sourcesafe, I think it is better not
    >in there.
    >
    >ralph,
    >
    >can you give me more details. Do you mean in windows explorer? or in
    >sourcesafe options?
    >
    >Thanks
    >
    >--
    >Michael Culley
    >www.vbdotcom.com
    >
    >
    >"ralph" <nt_consulting32@SPAMhotmail.com> wrote in message
    >news:3bfc0924$1@147.208.176.211...
    >>
    >> "Michael Culley" <mike@vbdotcom.com> wrote:
    >> >Every time I try to check out a DLL project file whilst in a group I

    get
    >> the
    >> >error message 'failed to reload project'. Does anyone know a way around
    >> >this.
    >> >
    >> >TIA
    >> >
    >> >--
    >> >Michael Culley
    >> >www.vbdotcom.com
    >> >

    >>
    >> Make sure your project files (*.vbp, *.vbw, *.vbg, ...) are not

    >'read-only'.
    >


    Can't remember all the specific scenarios and details but the failure is
    always related to one of the "project" files being 'read-only'.

    It is a "pain-below-the-navel" when working with VB projects. Environments
    such as VC++ will warn you and allow you to make the correction. VB is rather
    pissy.

    M$ has officially NOT supported putting the group file in VSS, but this is
    mostly because of the problems you can run into if it is not "read-write".
    Also having "Remove Local copy after Add or Check In" selected in VSS can
    cause problems, as well as checking in and out separate files. For example,
    you can get the error if one person only checks out one form, makes changes,
    checks the form back in - the next person to check out the entire project,
    will get the error. You have to close down, reload the project to "re-sync"
    the files and store.

    (VB loves to write to the 'hidden' headers - even if it doesn't write anything
    new or write anything at all - it just needs to feel it can if it wanted
    to ... I dated a girl like that once. <g>)

    It isn't just VSS, VB doesn't play nicely with StarTeam or PVCS either. VB
    likes to 'OWN' everything, everytime it is invoked.

    Your best options is to not remove files on check in, check out the entire
    project (even if making one small change), and make sure everything is 'read-write'
    before opening the project.

    Note: VSS behavior appears to be better in VS.NET.



  6. #6
    Thomas Eyde Guest

    Re: Bloody Sourcesafe!

    I've been so used to it that Alt-F-1 is hitted automaticly. It's funny how
    reloading the project group succeeds 99 out of 100, why did it fail at all?

    /Thomas

    "Michael Culley" <mike@vbdotcom.com> wrote in message
    news:3bfae162@147.208.176.211...
    > Every time I try to check out a DLL project file whilst in a group I get

    the
    > error message 'failed to reload project'. Does anyone know a way around
    > this.
    >
    > TIA
    >
    > --
    > Michael Culley
    > www.vbdotcom.com
    >
    >
    >
    >




  7. #7
    Michael Culley Guest

    Re: Bloody Sourcesafe!

    Whats Alt-F-1 do?

    It succeeds most of the time on your machine? On mine it always fails.

    --
    Michael Culley
    www.vbdotcom.com


    "Thomas Eyde" <thomas.eyde@online.no> wrote in message
    news:3bfda077$1@147.208.176.211...
    > I've been so used to it that Alt-F-1 is hitted automaticly. It's funny how
    > reloading the project group succeeds 99 out of 100, why did it fail at

    all?
    >
    > /Thomas
    >
    > "Michael Culley" <mike@vbdotcom.com> wrote in message
    > news:3bfae162@147.208.176.211...
    > > Every time I try to check out a DLL project file whilst in a group I get

    > the
    > > error message 'failed to reload project'. Does anyone know a way around
    > > this.
    > >
    > > TIA
    > >
    > > --
    > > Michael Culley
    > > www.vbdotcom.com
    > >
    > >
    > >
    > >

    >
    >




  8. #8
    Thomas Eyde Guest

    Re: Bloody Sourcesafe!

    Alt-F opens the file menu, 1 selects the first project in the MRU list.
    But you're right, it does not always work. It works only on project groups.

    Seems like VB is so "intelligent" that it senses the project is already
    loaded. Somehow it's not so "intelligent" when the project is a group.

    /Thomas




  9. #9
    Michael Culley Guest

    Re: Bloody Sourcesafe!

    hehe, I have an addin the routinely nukes my menus and all of the MRU list
    was gone.

    --
    Michael Culley
    www.vbdotcom.com


    "Thomas Eyde" <thomas.eyde@online.no> wrote in message
    news:3c01770e@147.208.176.211...
    > Alt-F opens the file menu, 1 selects the first project in the MRU list.
    > But you're right, it does not always work. It works only on project

    groups.
    >
    > Seems like VB is so "intelligent" that it senses the project is already
    > loaded. Somehow it's not so "intelligent" when the project is a group.
    >
    > /Thomas
    >
    >
    >




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center