Hey Joe, I'm finally looking into customizing the VS Publish feature. The scenario is that when I develop locally, I've copied the database and sites file structure down from the production server for local testing. Needless to say, I don't want to publish back any of those files during upgrades.

I noticed that Data\Sites\1\media is in the ExcludeFoldersFromDeployment section. But really, for most developers, wouldn't it be better to exclude Data\Sites completely, assuming a separate webmaster is maintaining skins and other site content, there may be entries in SharedFiles, etc.?

It's unfortunately that the settings are right within the csproj file. I'd prefer not to customize mojoPortal.Web.csproj, but if my needs are incompatible with yours I can certainly do that. For instance, I know it may be important to you to publish skins along with your updates, if you're working on those locally.

Also, I've noticed that there are a handful of XML files under Data\Sites\1 that are under source control. How critical are those files to proper site operation, and how often are they updated?

Thanks,

Jamie

Hi Joe, sounds good. I think it makes sense that the non-recommended deployment method will be the one needing to use a workaround. I'll keep an eye out for any confused developer posts here and help to educate as needed.

Jamie