Are you annoyed?
-
Nick Hodapp (MSFT) wrote: I'm looking for customer feedback (evidence) that the VC.NET 2002 (and even 2003) project system exhibits a real-world problem that affects your adoption of the tool. In particular, that you are annoyed with how the environment displays unnecessary messages during the build process about how projects in the solution are up to date. My guess is that it would be annoying if you had a lot of projects but, at present, I don't. One incredibly annoying thing is that the filter system for the documentation is broken. For example, if I filter by Platform SDK, then the "User Interface Design and Development" section is missing a whole lot of stuff including the "Windows User Interface" subsection containing Controls, Resources, User Input and Windowing (which includes Dialogs). As a consequence, I never use the filters, which means I have to wade through acres of irrelevant material to get to what I want. Edit: Integrating the "Favourites" with the IE Favourites was a really bad idea; it just creates another folder layer that I have to go through to get to what I want. John Carson
John Carson wrote: Edit: Integrating the "Favourites" with the IE Favourites was a really bad idea; it just creates another folder layer that I have to go through to get to what I want. I agree.
David Wulff
Hanging on this wire Waiting for the day where I'll have to choose Cursed by love so dire
-
That's what I do. :rolleyes: But then I often use messages and DDX functions that ClassWizard can't handle anyway. ;) Anna :rose: Homepage | My life in tears "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work. Trouble with resource IDs? Try the Resource ID Organiser Visual C++ Add-In
-
Nick Hodapp (MSFT) wrote: I'm looking for customer feedback (evidence) that the VC.NET 2002 (and even 2003) project system exhibits a real-world problem that affects your adoption of the tool. Sure, here you have it: 1. It's slow. Really really slooooow. 2. It's buggy, at least 2002 version crashes way too often and then it just re-starts (betting I won't notice or what?). Even a simple operations like adding the class for a dialog puts it down. 3. Lack of backward-compatibility. E.g. I can convert the VC60 project to the new VC70 project, but then if I change some settings I can't export it back to VC60. There is a tool at CP that does that, but IMHO that should be build-in. And all the VC60 addins are not working any more, but it should be simple to implement a proxy interface to allow them to operate. People are like spaghetti - you need to pull them, not to push them. 4. It's lame at times. It has many fesatures of VC60 missing and so it doesn't feel like an upgrade but rather the opposite. E.g. most of the code wizards are very simplistic and look like "5 minutes of work just before the relase". Then, once you get to those wizards you may notice that even the edit boxes there are screwed - I can't get the right-click menu to copy/paste stuff!? 5. It does stupid things. One example is the source control support where it creates some temporary files, adds then to source safe, then checks them out and then removes them. That effectively fills the history of changes with lots of noise and make the history view pretty much useless. It also tends to add the "afxwin.h" include here and there for no reason. Time to stop the micro-management I tell ya... As for the messages - the general rule applies that if it goes to the output window then it's fine. If it pops-up and asks me to take some action then it's probably bad. If it pops-up just to tell me something, but it gives me only an "OK" button to confirm that it's very bad.
/* I C++, therefore I am... */
George wrote: source control support where it creates some temporary files, adds then to source safe, then checks them out and then removes them I've wondered about that myself at times.
Without nipples, breasts would be pointless.