Publishing using Visual Studio

I need a mechanism to deploy code to production on an IIS server.   I was looking at the publish function in Visual Studio.  I'm using VS 2010.   The publish function seems to always copy all files, and it prompts me that it will delete all files in the target location.   I want just changed files to be deployed.  Is this a limitation of VS 2010?   Do I need a later version?
Who is Participating?
Randy DownsOWNERCommented:
It's easier to just copy your files into the IIS folder.
käµfm³d 👽Commented:
Out of curiosity, why wouldn't you just copy everything? If it's because of versioning, then that's what source control and assembly versions are for.

AFAIK, "Publish" outputs all files necessary for the application to run, regardless of which files were changed. You might look into XCopy deployment.
HLRosenbergerAuthor Commented:
I was not sure just copying all the files was the way to go.  but that's what I ended up doing.  I'm using a utility called FreeFileSync, which I really like, and in my opinion me much better than SyncToy.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.