VS2K5 doesn't compile/execute latest code

[=?Utf-8?B?QWRpbCBBa3JhbQ==?=]

I posted this question in vsnet.ide newsgroup about more than a week back but

didn't get any single response yet therefore, reposting again same to several

newsgroups.

When I run my C# WinForms project either by pressing F5 or clicking Start
button on toolbar, it sometimes doesn't execute the currently changed code
and runs previously compiled code and this strange thing happens occasionally
no matter its started in Debug or Release mode.

I have tried all the related options in VS=>Tools =Options =Projects and
Solutions =Build and Run, but problem not solved. Sometimes it compiles the
fresh code and sometimes not so, I can't mention the exact steps to reproduce
the behaviour. This problem happened to me hundreds of times during
development of my current project and there is no doubt in it. The only way I
found to workaround this problem is renming both the "bin" and "obj" folders.
It was so much frustrating because sometimes I am checking the effect of some
code but its actually not compiling it and breakpoints also doesn't work if

old code is running and on breakpoints it says that code is changed... etc.

I had this problem in VS2005 and I was anxiously waiting for final release
of SP1 and recently after upgrading to SP1 the problem is still there as it
is.

Does anybody experienced same problem with VS2K5, and how it can be fixed?

When will MS releases patch to fix it?

[Cor Ligthert \(MVP\)]

Because you have posted this to the VB.Net group, did you try it already
with VB.Net?

Cor

"Adil Akram" <Ad*******@discussions.microsoft.comschreef in bericht
news:6B**********************************@microsof t.com...

>I posted this question in vsnet.ide newsgroup about more than a week back
but

didn't get any single response yet therefore, reposting again same to
several

newsgroups.

When I run my C# WinForms project either by pressing F5 or clicking Start
button on toolbar, it sometimes doesn't execute the currently changed code
and runs previously compiled code and this strange thing happens
occasionally
no matter its started in Debug or Release mode.

I have tried all the related options in VS=>Tools =Options =Projects
and
Solutions =Build and Run, but problem not solved. Sometimes it compiles
the
fresh code and sometimes not so, I can't mention the exact steps to
reproduce
the behaviour. This problem happened to me hundreds of times during
development of my current project and there is no doubt in it. The only
way I
found to workaround this problem is renming both the "bin" and "obj"
folders.
It was so much frustrating because sometimes I am checking the effect of
some
code but its actually not compiling it and breakpoints also doesn't work
if

old code is running and on breakpoints it says that code is changed...
etc.

I had this problem in VS2005 and I was anxiously waiting for final release
of SP1 and recently after upgrading to SP1 the problem is still there as
it
is.

Does anybody experienced same problem with VS2K5, and how it can be fixed?

When will MS releases patch to fix it?

[serdar]

On 31 Ocak, 13:36, Adil Akram <[e-mail]>
wrote:

I posted this question in vsnet.ide newsgroup about more than a week back but

didn't get any single response yet therefore, reposting again same to several

newsgroups.

When I run my C# WinForms project either by pressing F5 or clicking Start
button on toolbar, it sometimes doesn't execute the currently changed code
and runs previously compiled code and this strange thing happens occasionally
no matter its started in Debug or Release mode.

I have tried all the related options in VS=>Tools =Options =Projects and
Solutions =Build and Run, but problem not solved. Sometimes it compiles the
fresh code and sometimes not so, I can't mention the exact steps to reproduce
the behaviour. This problem happened to me hundreds of times during
development of my current project and there is no doubt in it. The only way I
found to workaround this problem is renming both the "bin" and "obj" folders.
It was so much frustrating because sometimes I am checking the effect of some
code but its actually not compiling it and breakpoints also doesn't work if

old code is running and on breakpoints it says that code is changed... etc.

I had this problem in VS2005 and I was anxiously waiting for final release
of SP1 and recently after upgrading to SP1 the problem is still there as it
is.

Does anybody experienced same problem with VS2K5, and how it can be fixed?

When will MS releases patch to fix it?

i think u copy project and build so program debug previous.
u must change project file and then build.

[RobinS]

SP-1 for Visual Studio 2005 is final.

Robin S.
---------------------------------------------------
"Adil Akram" <Ad*******@discussions.microsoft.comwrote in message
news:6B**********************************@microsof t.com...

>I posted this question in vsnet.ide newsgroup about more than a week back
but

didn't get any single response yet therefore, reposting again same to
several

newsgroups.

When I run my C# WinForms project either by pressing F5 or clicking Start
button on toolbar, it sometimes doesn't execute the currently changed
code
and runs previously compiled code and this strange thing happens
occasionally
no matter its started in Debug or Release mode.

I have tried all the related options in VS=>Tools =Options =Projects
and
Solutions =Build and Run, but problem not solved. Sometimes it compiles
the
fresh code and sometimes not so, I can't mention the exact steps to
reproduce
the behaviour. This problem happened to me hundreds of times during
development of my current project and there is no doubt in it. The only
way I
found to workaround this problem is renming both the "bin" and "obj"
folders.
It was so much frustrating because sometimes I am checking the effect of
some
code but its actually not compiling it and breakpoints also doesn't work
if

old code is running and on breakpoints it says that code is changed...
etc.

I had this problem in VS2005 and I was anxiously waiting for final
release
of SP1 and recently after upgrading to SP1 the problem is still there as
it
is.

Does anybody experienced same problem with VS2K5, and how it can be
fixed?

When will MS releases patch to fix it?