User323983933 posted
I read all that, and the logical choice is Content ->
Copy if Newer.
I did that and...
It's still spending over an hour copying these (unchanged) flag icons during a publish.
Here's the DIR info...
Total Files Listed:
3641 File(s) 24,150,403 bytes
I am using Publish to File Folder (to a VPN folder at work). In this case I am NOT having it clean the folders prior to publish. So the icons are there. I do NOT want to tag tham as do not copy, or None because sometimes we wipe the folders
on a publish and they would be missing if we did that.
Maybe I should set up IIS with a virtual folder containing the images and publish them as a separate solution.
Is there a way to make a second project with just the icons and have them publish separately to the same destination?
UPDATE:
I still marvel at how LONG it takes to publish these small files. I stopped my publish after an hour and 6 minutes and it was nowhere near done.
Incidentally, with Content -> Copy if newer, all the icons were copied TWICE. Once in bin/content/images... and once in /Content/images. I changed them to
Build Action: None, Never Copy. I figure if anyone ever does a build with delete set I can copy them back in as needed.
But something is wrong. It's taking over a second to copy 600 byte files. Maybe the virus scanner is choking on them or something.
For now, I'm staying with Build Action: None, Never Copy and manually restoring the images if needed.
But what SHOULD have happened is that the publish function should have recognised and skipped the already published files.