Why is Visual Studio 2022 not publishing my most recent changes

Question

Why is Visual Studio 2022 not publishing my most recent changes

Neil Hinkle 15

I'm working on a vb.net web app and noticed yesterday that, when publishing to a local folder, it's not pushing out my most recent changes. I can see that they're in my repository when I push and pull. Everything is saved and working correctly when I debug but when I right-click on the solution and choose to publish, it is publishing files from days ago for some reason.

I was able to temporarily fix this last night by completely uninstalling Visual Studio, reinstalling it, and cloning the project from its repository. That finally resulted in the current files being published but the very next set of changes that I made were ignored. Resetting my preferences this morning did nothing to fix it either.

I haven't made any changes to my VS configuration and am running 17.6.5. I haven't seen that this is a known issue for it though.

Any suggestions on what to do here?

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Answer 1

Salvatore Strazzullo 11

Ancient bug that hasn't been solved yet as of Visual Studio 2022 v17.14.40 (not sure in VS2026). What I do is usually to delete the files in the build folder and retry, sometimes it also doesnt fix it, so the only thing that actually works is to delete the publish profile and make a new one

0 comments

Answer 2

Anna Xiu-MSFT 31,211 Microsoft External Staff

Hi @Neil Hinkle ,

Welcome to Microsoft Q&A!

Can you create a new project and check that it occurs in the specific project?

You can right-click on the changed file and manually publish it.

Sincerely,

Anna

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Neil Hinkle 15 Reputation points

2023-07-27T13:02:26.8033333+00:00

I threw together a quick webapp and that seems to have worked fine.

I also did some additional digging on the original project and it seems that something is going on with where it's writing the files. I have my Publish configuration set to release and the log shows that it's writing to obj/Debug but it appears to be copying the files from obj/Release to the target location, so whatever is happening, the files in the Release folder are not being updated. I tried creating a new profile but that didn't make any difference.

The good news is that I can always grab the most recent files from obj/Debug after publishing but that's still less than ideal.
Anna Xiu-MSFT 31,211 Reputation points Microsoft External Staff

2023-07-28T09:37:08.9866667+00:00

What is your build configuration? If it is Debug mode, please change it to Release and try again.

Besides, please check the permission to obj/Debug and obj/Release.
Zhitnitsky, Yuri 0 Reputation points

2023-07-31T15:55:53.25+00:00

I have exactly same issues with pulishing any Web Projects. It started after I upgrade VS from 17.6.3 to 17.6.5

It works only when I publish in Debug (any cpu) mode. If I choose Release (any cpu) then I get same issues.

During Publish in Release mode, VS builds in to \obj\Debug\AspnetCompileMerge\TempBuildDir, not \obj\release... folder and is where the issue starts
Jan Webber Macias 0 Reputation points

2023-08-03T02:01:16.7233333+00:00

I am experiencing the same problem, but it happens to all my existing projects. It seems like the publishing feature got stuck in time. This problem just came out recently in all of my current projects.
Michael Roush [KDHE] 5 Reputation points

2023-08-03T14:42:03.8533333+00:00

I began experiencing the same problem. Removing the obj completely, changing the build to Release, clean the solution, rebuild solution, publish. Seems to work. Just remember to change your build back to Debug. VS needs to fix this, it is less than ideal to go through so many steps.
Anonymous

2023-08-17T21:04:06.5233333+00:00

Behavior of the Publish tools clearly changed a couple of maintenance updates ago. I used to never worry about the active Run Configuration when publishing a new build - always leaving it on "Debug." I would just select my Test or Production Publish Profile and everything "worked."

@Michael Roush [KDHE] has the solution. Change to the Run Configuration that you want to publish and clean the solution before publishing.

Way to many steps. Bring back the old behavior, Microsoft! Or add a switch to the publish configuration to Clean the solution first!
John Janes 0 Reputation points

2023-09-06T16:08:04.59+00:00

Same issue. C# project, older framework (4.7.2). When I publish the site in release, it does not reflect page changes. I can sometimes publish an individual page as long as the changes are only HTML. If the changes are in the code itself, I cannot get the publish to reflect the changes.