VSS, Analyze, and Check-in Policy

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jsbell@liberty.edu - 31 Mar 2005 03:53 GMT

Is it necessary to check all files in for Analyze to work correctly? We are having some trouble with it and the DB Admin is saying we have to check in everything once a week, ready or not, in order to fix it. I have worked in other VSS environments where there was no such restriction. Additionally, the idea of checking in prematurely just to run Analyze seems risky to me. Isn't there a great potential for getting bad builds that way?

Any Ideas would be welcome ...

Thanks

Reply to this Message

Gene S. Berkowitz - 02 Apr 2005 14:47 GMT

> Is it necessary to check all files in for Analyze to work correctly? We are having some trouble with it and the DB Admin is saying we have to check in everything once a week, ready or not, in order to fix it. I have worked in other VSS environments where there was no such restriction. Additionally, the idea of checking in prematurely just to run Analyze seems risky to me. Isn't there a great potential for getting bad builds that way?
>
[quoted text clipped - 5 lines]
> Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

No, it is NOT necessary to check in files before running Analyze,
and as you infer, it's plain stupid to check in unfinished work.
Make sure the admin LOCKS the database, so nothing can CHANGE during
analyze. Is the admin running Analyze on the same machine hosting
the database, or is he running it from his workstation over the
network? Network issues can often cause problems, so it should be
run on the server, if possible.

--Gene

Reply to this Message

jsbell@liberty.edu - 04 Apr 2005 04:30 GMT

Thanks, Gene.

As to whether Analyze is being run from the network or a workstation, I will inquire along the lines you have suggested... Developing ...

Reply to this Message

VSS, Analyze, and Check-in Policy

Free Magazines