Mike
Sat Jan 15 05:56:05 CST 2005
WSS puts everything into the database.
But you can create a local drive on your client if it is running Office 2003
with
net use X: \\servername\xxx\doclib
where the http address of the doc lib is
http://servername/xxx/doclib
and get Cruise Control to watch that local drive for new files.
Whether this also solves your "automatically launch the build process" is
something I don't know (and would guess possibly not) because it's not wise
to do much more with that local drive version of the doc lib than list it or
copy files in and out of it.
[P.S. I'm assuming that with "SharePoint Server" you mean Windows SharePoint
Services server as you posted here - please use WSS or SPS 2003 in future so
we know exactly what you have.]
Mike Walsh, Helsinki, Finland
WSS FAQ at
http://wss.collutions.com
Please reply to the newsgroup
"Doug Clutter" <dougc@douglas-associates.com> wrote in message
news:0fbd01c4fa99$fec09230$a301280a@phx.gbl...
>I have an off-site developer who will need to upload a
> ZIP file to our Sharepoint server containing updated
> source code. Sharepoint seems to be putting this into
> SQL server but I would like to store the file in the file
> system.
>
> Why? Because I want CruiseControl to watch that
> directory for uploads and then automatically launch the
> build process using the newly uploaded file.
>
> If there is an easier way (and I'm sure there is) could
> somebody send me in another direction? TIA