RE: IIS Website versioning

> Working on something like this already, I've got a little
> program in C# that will "svn export" projects/directories
> for a particular revision number.

I like the idea of an export for live sites (keeps the .svn folders off the public web), but would like the head folder to be a checkout/update.

I am concerned that this may happen quite frequently during heavy development times and would like for the client to have uninteruped test time. Since the changes would be smaller than an export I think the chance of a user noticing a file missing would be signifigantly reduced. It would also cut down on network traffic and such.

If no one can think of a reason this is going to cause me grief, I'll just go ahead and do it. Like I said, I had a big problem (could not delete .svn folder while IIS was pointing at it) with this a long time ago (v0.26?) so I hope it just disappeared.

-----Original Message-----
From: tom@opgenorth.net [mailto:tom@opgenorth.net]
Sent: Tuesday, April 20, 2004 2:25 PM
To: Jeff Cave; users@subversion.tigris.org
Subject: Re: IIS Website versioning

Working on something like this already, I've got a little
program in C# that will "svn export" projects/directories
for a particular revision number. This gets called by my
post-commit hook. Fairly straight forward, and seems to
work well for what I need.

The biggest problem that I encountered was file permissions:
 I was trying to export to a network share, and I can't give
the System account that is running the program permissions
to write to the share.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 20 22:34:20 2004