So because VS default is usually 4-space tab indents and has no preference on the trailing slash, it will always differ with how the server prefers to do this using its 2-space indents. config files by the server always seem to reformat/re-indent entire sections using two-space indents, sometimes even jamming the "/>" part of self-closing tags against the last attribute value and sometimes not. The interesting thing is that any programmatic changes to. Ideally we want everybody who updates files in the core to use VS default settings for fomatting documents so that would be 4 space indents.Įven more ideally, we would do config transforms as part of the upgrade process but that's pretty complicated to pull off without possibly overwriting custom settings that shouldn't change (but this IS on my task list, just got bigger things to tackle for now). I am unsure of how we could facilitate consistency though, as I don't actually know why this is happening (haven't looked into it). I finally learned that WinDiff has the option to ignore whitespace differences and that really helps a lot. I feel your pain, this has been a pet peeve of mine for a LONG time. (Please feel free to close this issue as Won't Fix if it seems overly ridiculous!) Thank you. Normalizing these before check-in was occasionally only a minor hassle.įrom someone working "in the trenches" who recently went through and updated more than a dozen sites, I mention this in hopes the upgrade process could be made ever-so-slightly smoother in the future by minimizing the number of "diffs" between these files, and enforcing consistency across all of them.
(Yes, I know we can set our difference engines to ignore leading whitespace differences, but we still have the occasional difference in the last space before the "/>" of a self-closing tag which does requires manual attention.) I may be partially basing this request due to experience on a past project once with very strict diffing/check-in policies, because Visual Studio likes to format these files with tabs or 4 spaces, but when you programmatically update them on the server they are saved with 2 spaces. We are going through these files one by one, site after site, and find that most of the "diff" changes brought to our attention during the latest round of upgrades seem to be due to whitespace issues. This is such a minor thing I am afraid to even mention it, but thought I would anyway in the hopes that enforcing a consistent formatting in these XML config files might somewhat expedite/simplify the upgrading/diffing process.Īs part of the recommended upgrade process, we are asked to diff the contents of /config/ as well as /web.config.
0 kommentar(er)
