Re: edit and continue

Tech-Archive recommends: Fix windows errors by optimizing your registry

"Michael C" <nospam@xxxxxxxxxx> wrote in message
news:%23vMc5MY5FHA.156@xxxxxxxxxxxxxxxxxxxxxxx
>
> No, it was just a general statement that it is more than compensated for
> in other areas.
>
>> Make up for it? There is no way to make up for it. Who cares about the
>> 100 bells and whistles if the feature they use most is missing? iow, you
>> can give me a Rolls Royce but it won't do me a bit of good without a
>> drivers seat.
>
> The immediate window is not the be all and end all and it's certainly not
> the drivers seat. *Real* features such as inheritance more than make up
> for it.

Oh yeah... inheritance helps while debugging... I must've forgotten.

>> We've been using SourceSafe since 1998. Not one single crash. Not one
>> single corruption. The only thing that can even be considered an
>> annoyance is the error dialog you get when you attempt to check out parts
>> of a group project.
>
> Are you using the same sourcesafe I'm using. The one that comes up with
> "failed to reload project" *every* time you check out a dll. The same one

Failed to reload project is not a crash. It's very explainable. If you have
a group project, the project's VBP files are read-only. When you check one
out, VB attempts to replace the compiled reference(s) with references to the
VBPs instead. It fails to do this because there are still Read-Only files in
the project and reports that error. No big deal. Just reload the group.

> that doesn't let you modify usercontrols *every* time you check them out.

I have no idea what you mean there. The Read-Only's still set?

> The same one that seems to rollback changes at random and crashes on a
> daily basis. I'm very interested to know what you're doing to stop source
> safe crashing vb6.

Using version 6.0c. Zero random rollbacks (I can see why this would be a bad
thing), zero crashes, zero real problems.

> Posting this was highly relevant to this group. Not everyone reads vs05
> ads (i didn't even know they existed) and I bet a significant number of
> people reading this thread didn't know. I didn't know until someone in
> support pointed it out to me.

Man... E&C's all I've been hearing about since Beta 1.

>> get eh? Make it so the developer wants to get the work done and close the
>> project as fast as they can to avoid the disgust of looking at the code.
>> Perfect.
>
> Get over it ken. There is nothing wrong with C style code, after a while
> you'll understand it is much better and much more aimed at the
> professional. The beginner needs to type "Dim x as int" or "ByVal X as
> int", the professional works on code daily and would much rather type "int
> x". If you have more of an open mind you'll look back at vb6 one day and
> think how ugly it's code is.
>
> Michael

That all lower case 'int x' is beautiful? C devs are so lazy they can't
complete the word 'Integer' or press shift while typing?.... and VB is ugly?
What ever doood.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..


.

Relevant Pages