I use VB for prototyping and for quick and dirty apps. I would never release a commercial app written in VB for a number of reasons, some of them are valid, some ego. 1) I can tell a VB app just by looking at it. For some reason, it just "feels" different to me, and has some kind of subtle feel to it, this gives me an unconscious negative feeling about the app. I know other programmers probably have the same feeling as well - Chalk it up ot ego I suppose. The reason that it feels different is probably due to the lack of skill of most VB designers, and the ease of which you can design things. Therefore newbie designers tend to make interfaces more complicated because it's not that much work. In VC, a complex interface is more work and you have an incentive to make it simpler. 2) VB is difficult to scale into larger apps. VB doesn't provide a good code management system, and the interface encourages putting code into the UI versus writing business logic. Note that I said "encourages" not "forces". I think it requires a lot more self-discipline as a programmer to create "good" VB code than it does in VC simply by nature of the UI. So, for me, VC takes less effort for large scale projects than VB does, this translates into faster development cycles and is a very real reason for me to not use it. 3) VB *CAN* be used to write commercial quality apps, but most people take the easy route and use data controls and other simple mechanisms which provide a very generic look and feel. I like my apps to have a unique look to them, and go out of my way to make them asthetically pleasing. The more asthetically pleasing it is, the less strain the user will have in using it. I can do this much easier in VC than in VB. VB's "easy" stuff also locks you into a more generic look.