Member Avatar for kenth21v

I am experiencing a similar problem everytime I stay too long in coding.
here is the problem: When I EDIT a code, or move a position of a button or textbox or anything, or any other changes is done, and i debug it, the changes I made won't appear.
(the one that will play will be the one that not changes, for example: the moved button is still in its original position)

this happens all the time. Am I accidentally pushing a button ? This problem is ruining my mood all the time.. Please help me about this. Thanks.

  • 2 Contributors
  • 3 Replies
  • 333 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by codeorder

Dani AI

Generated

Short expert note: this is a common Visual Studio build/cache issue and there are fast, safe fixes you can try before reinstalling. OP reported that a full Rebuild fixed the symptom (and ’s reinstall did not), which is consistent with a stale-output problem — below is why that happens and a compact checklist to fix it reliably.

Visual Studio does incremental builds by default (only changed files are recompiled), while a Rebuild first cleans output and then compiles everything anew. Modern VS also uses a “fast up‑to‑date” check that can incorrectly decide a project does not need rebuilding, so the IDE may run an older binary. Forcing a clean/full build removes that stale state. (learn.microsoft.com)

Quick checklist (do these in order):

  • Save All, then Build → Clean Solution and Build → Rebuild Solution.
  • If the problem persists, close VS and delete the solution’s hidden .vs folder plus every bin and obj folder, then restart VS.
  • Confirm the right project is the startup project (and check Configuration Manager so the project is included in builds).
  • Try a command‑line rebuild to rule out IDE caching:
msbuild MySolution.sln /t:Rebuild /p:Configuration=Debug
  • To delete build folders from PowerShell (run from the solution root):
Get-ChildItem -Path . -Recurse -Directory -Force |
  Where-Object { $_.Name -in @('bin','obj') } |
  Remove-Item -Recurse -Force -ErrorAction SilentlyContinue

(Use the Developer Command Prompt or msbuild/dotnet-msbuild to run the rebuild if you prefer.) (fsse8info.wordpress.com)

Extra tips if it still happens: increase MSBuild/IDE verbosity to Diagnostic and watch the up‑to‑date messages to see which inputs/outputs triggered the skip; check for extensions that replace the build (ReSharper Build, custom targets); and if your project has custom generated outputs add the appropriate UpToDateCheck inputs or (as a last resort) disable the fast up‑to‑date check for that project. If none of this helps, migrate sources into a fresh project to rule out corrupted solution/VS state. (github.com)

Recommended Answers

All 3 Replies

Member Avatar for codeorder

Try Repairing/Reinstalling Visual Studios. Could be an internal issue w/VS, although...
If this only happens in one project, cloning/restarting the project might and possibly will fix the issue.

I personally would Reinstall(after saving my.Cool VS.Settings, If you got any), to get a new copy of VS. Hope this helps.

Edited by codeorder because: n/a
Member Avatar for kenth21v

Sorry for late reply.
I tried reinstalling but the problem still occurs.
Btw, "Rebuild Solution" does the job.
Tnx !

commented: providing.solution to own thread.:) +12
Member Avatar for codeorder

I have had the same issue years ago and could not figure it out.:(Thanks for solution.:)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.