3 ms·
It seems to this curmudgeon is that the bug is in the whole metaphor of a "project file" being storage for a bunch of UI state set in a bunch of configuration t
by ajross 13y ago
It seems to this curmudgeon is that the bug is in the whole metaphor of a "project file" being storage for a bunch of UI state set in a bunch of configuration tools and not, y'know, part of the source code of the project and subject to the same kind of engineering process.
You play this kind of game with "automation" and you get burned. Build, configuration and deployment management are hard software problems and they need to be solved by smart people and real tools, not checkboxes and file selectors.
- csmuk 13y agoThis. Visual Studio to be blunt is a fucking nightmare in this department. It's cost us hours fixing configuration problems. We have 50 developers though so are a large team.
- blt 13y agoI agree. I love Intellisense but I wish Visual Studio would stay the fuck out of the way everywhere else. It's particularly annoying how all the checkbox settings are only applied to the active configuration unless you change a dropdown menu... can't even count how many times I made a change to Debug/x64 only and then had to go back and fix it later.
- malkia 13y agoSame here. I'm in the habit now of making sure that I've selected all target configurations, then all target architectures and then put the settings. But even then, I need different settings for debug/release or x86/amd64 - and it's not really helping when there is incosistent naming across SDK's coming from Microsoft itself - where you can't match with one variable (say $(Target)) the given architecture, and it seems every group at Microsoft follows different conventions of how to name things.
- bruceboughton 13y agoThe project file is a source file and should be in source control.
- ajross 13y agoThat gets to a semantic argument. Yes, the project file is a text file that can be editted. But editting it is not the natural form for making changes, which is an important part of the definition of "source code". The natural way you make changes to it is to click on junk in a GUI, and that means your changes are going to be inherently filtered through whatever policy decisions the GUI tool made. And that's a huge flaw from the perspective of engineering process. You can't hack what you can't see, basically. And changes to the project file (or whatever other "wizard guided" IDE output you're using) are opaque by definition.
- nightski 13y agoIf it is a text file you manually edit, then those changes are going to be inherently filtered through whatever policy decisions the tool that reads that file makes. I am having a hard time truly understanding the difference (not that we use VS stuff for deployment anyways, but that is for other reasons). A developer could add custom deployment info to the manual file and accidentally commit it just as easily. You just do not like GUIs (which is a perfectly acceptable stance) but it has nothing to do with some fundamental difference.
- curveship 13y agoThis is uninformed FUD. You can "see" what's in VS's project files just fine. The file format is straightforward XML with fairly obvious semantics. Having worked with both VS's .csproj files and UNIX makefiles, .csproj is far far easier to understand and make changes to. I dive into it all the time. The most common case is when I've got WIP changes that conflict with another dev's checkin and I have to resolve them by hand. Just because they supply a GUI doesn't mean it's the only way to change project settings. I'm not sure what led you to believe that.
- bradford 13y agoThere's no 'natural' way of editing the project files: if you think that the 'natural' way of doing it is by clicking junk in a gui, then you are assuming too much. While I'm probably in the minority, I edit my *.csproj files by hand and build from the command line for several of my projects. I do this for the exact reasons that you mention: I like control in the engineering process. I'm unhappy that VS 2013 is putting user settings in the proj file willy nilly and I hope that it's fixed soon.