Re: [GD-Windows] VS.net rants, was Re: VC++ lag
Brought to you by:
vexxed72
From: Ben C. <be...@gu...> - 2003-06-13 18:11:05
|
On Friday, June 13, 2003, 1:44:24 PM, someone wrote: > I can add a few cents here, too... ...and a "few" more... 1) Various source-control operations cause the Solution Explorer to spend several minutes jumping randomly between files in the project (apparently opening/closing/saving them or whatever) if you have many windows open. 2) In fact, can the Solution Explorer jump-to-current-file behaviour be turned off? It's occasionally useful, but far more often just annoying. 3) Editing multiple project properties at once is buggy, as is editing multiple configurations - frequently the properties window mysteriously looses changes, vanishes altogether, displays "there are no properties for the selected item", or, in extreme cases, simply crashes VS.net entirely. I've had to edit the .vcproj files by hand a couple of times to make changes thanks to this... 4) If you do a "get latest" from within Sourcesafe recursively, and several .vcproj files are updates, then VS.net only notices the first one that's changed, and blindly goes on using the others without reloading them. 5) "Get latest" from within the IDE is useless because it seems to operate on the *current* .vcproj file, not the one in Sourcesafe (or a merge of the two), and hence misses newly-added files. 6) Custom build step dependencies are crippled - it seems impossible to set up a configuration that allows (for example) compiling a vertex shader and then "incbin-ing" the resulting bytecode into a header file for inclusion in the project in such a way that everything rebuilds correctly without resorting to multiple rebuilds and/or abuse of "touch" on things. 7) Can we have an option to turn off the task list? It's just a pointless recap of the information in the build window (usually with the important bits missing), and more often than not you spot the error in the build window, go to read it and... blam, you're looking at the task list instead because the build just aborted. 8) An option to suppress the comments dialog when checking out files would be good. We never use them, but I've lost track of how many checkouts now have comments along the lines of "nt blah=0;" because we're all used to just hitting ENTER to clear the "check out now?" prompt... 9) I haven't tried too hard to make this work so it could just be a misplaced setting, but Japanese SJIS text support in the editor is broken (it worked in VC6). 10) And yes, yet another plea for a one-step "show settings for current project and build" button. And, if possible, a convenient way to change the "Debug->Command line parameters" setting for the current project (in fact, the option to have that as a edit box on the toolbar would be best). ...er.. I think I'll stop now ^-^; -- Ben Carter - Neko Technologies - be...@gu... http://www.neko-tech.com/ - http://www.absoluteterror.com/ ---------------------------------PGP Key available on request--- "Broken mirror, a million shades of light, the old echo fades away. But just you and I can find the answer, and then we can run to the end of the world." - Small of two pieces, Xenogears |