RE: Re: VS2003-compiled WinCvs doesn't work for me...

Oliver,

I've just built and tested on VS.NET 2003 and can't reproduce the problem you reported - but my "status" problem has been fixed.  So we'll probably ship this build with the CVS Suite next week.

I'm hoping to submit my feature patches early next week, they are:
* adding the option to use the CVSNT wizard
* storing registry variables in ASCII format (not BINARY format)

When you built using VS.NET 2003 did you ensure that the platform SDK you were using was the one that came with VS.NET 2003 (ie: move the priority down for any later installed SDK's)?

Regards,


Arthur Barrett


-----Original Message-----
From:	[email protected] on behalf of Oliver Giesen
Sent:	Wed 3/8/2006 10:41 PM
To:	[email protected]
Cc:	
Subject:	RE: [cvsgui-dev] Re: VS2003-compiled WinCvs doesn't work for me...

> Just hoping there are no other subtle bugs resulting 
> from the port in there.

Maybe I shouldn't have mentioned that... seems like just that has happened. I cannot reproduce it reliably yet but it happens often enough on at least one machine:

When updating, committing or status'ing (and possibly other Entries-modifying commands as well) using the VS2003-built WinCvs I currently get the following error in 9 out of 10 cases:

cvs [update aborted]: cannot rename file CVS/Entries.Backup to CVS/Entries: Permission denied

On the same machine, I never get this with my VC6AE-build (built from the same set of sources) - that is: I never get this when I run it on its own. When I have the VS2003 build running in parallel, I also get this but with a slightly different touch. I.e. in that build I get additional output before the actual error appears:

Unable to rename file CVS/Entries.Backup to CVS/Entries for 1 second, still trying...
Unable to rename file CVS/Entries.Backup to CVS/Entries for 2 seconds, still trying...
<.snip.>
Unable to rename file CVS/Entries.Backup to CVS/Entries for 9 seconds, still trying...
Unable to rename file CVS/Entries.Backup to CVS/Entries for 10 seconds, giving up...

Looks like the VS2003 build is somehow keeping a lock on the Entries file. Then again, I have no trouble manually deleting the Entries file and renaming the Entries.Backup file even while WinCvs is running. Both WinCvs instances were using the same CVSNT client binary (2.0.51d).

I'll just drop back to my VC6AE build for now. Got to get some work done.
Just thought I'd drop a note in here so you know there's possibly something lingering still...

Cheers,

Oliver
----	 ------------------
MSN:   [email protected]
ICQ:	 18777742	(http://wwp.icq.com/18777742)
Y!:    ogiesen










[Non-text portions of this message have been removed]



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/