pinkmonkey4ever wrote:

> I have a VC6 ANSI C (console) project that I have recompiled sucessfully
> under VS2005.
>
> However, when I attempt to debug the code (step through) - my
> breakpoints are disabled (msg : "beakpoints will not be hit"), and worse
> still - I find that instead of steopping through my code, I am stepping
> through a file named crt.exe - which guessing from the function names in
> the file (as well as the file name itself) - is something to do with the
> CLR (i.e. .Net stuff).
>
> I can't understand how this can be. This is a simple ANSI C console
> project that makes ABSOLUTELY NO use of the CLR. I've checked and
> re-checked my project settings and AFAICT, everything looks ok - also, I
> am at my wits end. Does anyone have an idea as to what may be causing
> this bizzare behaviour?

"pinkmonkey4ever" <fluffy@slippers.com> wrote in message
news:Y7ydnd2_a7afKBnbnZ2dnUVZ8vudnZ2d@bt.com...
>I have a VC6 ANSI C (console) project that I have recompiled sucessfully
>under VS2005.
>
> However, when I attempt to debug the code (step through) - my breakpoints
> are disabled (msg : "beakpoints will not be hit"), and worse still - I
> find that instead of steopping through my code, I am stepping through a
> file named crt.exe - which guessing from the function names in the file
> (as well as the file name itself) - is something to do with the CLR (i.e.
> .Net stuff).
>
> I can't understand how this can be. This is a simple ANSI C console
> project that makes ABSOLUTELY NO use of the CLR. I've checked and
> re-checked my project settings and AFAICT, everything looks ok - also, I
> am at my wits end. Does anyone have an idea as to what may be causing this
> bizzare behaviour?

SvenC wrote:

> Hi,
>
> "pinkmonkey4ever" <fluffy@slippers.com> wrote in message
> news:Y7ydnd2_a7afKBnbnZ2dnUVZ8vudnZ2d@bt.com...
>
>> I have a VC6 ANSI C (console) project that I have recompiled
>> sucessfully under VS2005.
>>
>> However, when I attempt to debug the code (step through) - my
>> breakpoints are disabled (msg : "beakpoints will not be hit"), and
>> worse still - I find that instead of steopping through my code, I am
>> stepping through a file named crt.exe - which guessing from the
>> function names in the file (as well as the file name itself) - is
>> something to do with the CLR (i.e. .Net stuff).
>>
>> I can't understand how this can be. This is a simple ANSI C console
>> project that makes ABSOLUTELY NO use of the CLR. I've checked and
>> re-checked my project settings and AFAICT, everything looks ok - also,
>> I am at my wits end. Does anyone have an idea as to what may be
>> causing this bizzare behaviour?
>
>
> Did you build and run the debug version?
>
> --
> SvenC

"pinkmonkey4ever" <fluffy@slippers.com> wrote in message
news:Y7ydnd2_a7afKBnbnZ2dnUVZ8vudnZ2d@bt.com...
>I have a VC6 ANSI C (console) project that I have recompiled sucessfully
>under VS2005.
>
> However, when I attempt to debug the code (step through) - my breakpoints
> are disabled (msg : "beakpoints will not be hit"), and worse still - I
> find that instead of steopping through my code, I am stepping through a
> file named crt.exe - which guessing from the function names in the file
> (as well as the file name itself) - is something to do with the CLR (i.e.
> .Net stuff).