actually with tortoisesvn, you don't have to check out and then export it in two steps. you can make a folder, right click it and pick export directly from the context menu.
"actually with tortoisesvn, you don't have to check out and then export it in two steps. you can make a folder, right click it and pick export directly from the context menu."
That's what you do with commandline svn too.
jared, once you select the "export" option in the context menu, tortise will then ask you where you want to export a copy of the files to, this will then export a "fresh" copy of the updated files to another directory of your choosing. That directory will be as static as just exporting files from a zip which you can do whatever you want with then.
If at any time afterwards you do another SVN update on a local repository, you'll have to export another fresh copy again if you want to upload it without all the .svn files/folders. It's just the way windows manages the hidden files and folders as opposed to other systems so you'll end up with tons of extra unecessary files if you're just copying the local svn repository manually.
You can export each time a version bump comes along or even export an earlier version if you'd like to and keep a local copy for yourself if you run into trouble. If it starts asking for a login/password, then just realize you're not supposed to be playing with that portion :)
Comments
actually with tortoisesvn, you don't have to check out and then export it in two steps. you can make a folder, right click it and pick export directly from the context menu.
i don't know if you're using tortoisesvn, though