Error publishing (to Azure) dotnetcore app after upgrading from dotnetcore 2.0 to 2.1

Background:

We just upgraded from dotnetcore 2.0 to 2.1. Most stations had the build successfully except 1, but that was because he had some dependencies projects of his own, we changed them all to 2.1 and he also had referenced one of them both in Assembly and in Projects, we removes the assembly as suggested in stackoverflow.

Then while trying to publish we got this exception in most stations:

Assets file '(project)\obj\project.assets.json' doesn't have a target for '.NETCoreApp,Version=v2.0'. Ensure that restore has run and that you have included 'netcoreapp2.0' in the TargetFrameworks for your project.

Most answers hiding in github mentioned deleting the bin and obj, and than help a couple of stations.
We then also Clean and Rebuild, but that also helped just a couple more.

Eventually by mistake I played and changed the Publish Configuration Settings, Save, Publish, and back to old configuration and it worked. I guess that it cleaned it own publish conf cash.









Comments

  1. sclinbioSeptember 11, 2023 at 9:02 AM

    This is a great post. I like this topic.This site has lots of advantage.I found many interesting things from this site. It helps me in many ways.Thanks for posting.our sclinbio.com 🙂

    ReplyDelete
  2. DigitalBrollyJuly 12, 2025 at 7:35 AM

    Thanks for sharing this! Upgrading between .NET Core versions can often cause unexpected issues, especially with lingering references and mismatched TargetFrameworks. Your note about checking the project.assets.json file and eliminating dual references (Assembly + Project) is a key takeaway. This post will definitely help others facing similar publish-time errors after migration.

    AI Powered Digital Marketing Course In Hyderabad.

    ReplyDelete
  3. azuretrainingAugust 22, 2025 at 4:23 PM

    "Your blog is quickly becoming one of my favorites. Every post offers real value, and this one is no exception."

    Azure Data Engineer Training In Hyderabad

    ReplyDelete
  4. DigitalBrollySeptember 4, 2025 at 2:53 PM

    This is a really useful write-up! The error with project.assets.json after upgrading from .NET Core 2.0 to 2.1 can be quite confusing, and your note about cleaning the publish configuration cache adds a practical troubleshooting step that many developers might overlook.
    Digital Marketing Course In Hyderabad.

    ReplyDelete
  5. GenerativeaimastersSeptember 24, 2025 at 2:48 PM

    Thanks for sharing this! Your solution to the .NET Core 2.0 to 2.1 upgrade error was very helpful. Changing the publish configuration settings worked for me too. Great tips.

    Generative AI Training In Hyderabad

    ReplyDelete
  6. FAST PREP ACADEMYOctober 6, 2025 at 10:58 AM

    Thank you for this insightful guide on troubleshooting Azure publishing errors in .NET Core applications. Your step-by-step approach, including checking SDK versions, verifying connection strings, and ensuring proper permissions, provides a comprehensive solution to common deployment issues. The emphasis on examining logs and utilizing diagnostic tools further aids in pinpointing the root causes of failures.

    At Fast Prep Academy, we emphasize the importance of mastering deployment strategies and troubleshooting techniques to ensure smooth application releases. Your article serves as an excellent resource for learners aiming to deepen their understanding of Azure deployments.

    ReplyDelete
  7. littuNovember 30, 2025 at 10:36 AM

    Thanks for breaking down the error scenario for Azure + .NET Core deployment — seeing your actual error and fix makes it easier for others who might run into something similar. The post helps demystify what can go wrong when deploying to cloud environments. For readers juggling projects and exam-style prep, sat coaching online by Fast Prep Academy might help you manage both smoothly.

    ReplyDelete
  8. Hey TempFebruary 3, 2026 at 7:40 PM

    This post is an incredibly helpful technical resource for developers navigating the complexities of Azure deployments! Providing a clear, step-by-step solution for the .NET Core "Error Publishing" issue—specifically identifying how temporary file locks or build configuration mismatches can disrupt the process—offers a practical roadmap for maintaining a smooth development workflow. I especially liked the focus on cleaning the solution and verifying the project’s target runtime, as these are often the small details that make the biggest difference in successful cloud integration. Just as a well-resolved technical error ensures system stability and performance, specialized medical expertise is vital for health, which is what we prioritize at our Multispeciality Hospital in Kadapa. Thanks for sharing these valuable software development and cloud computing insights!

    ReplyDelete
  9. Hey TempFebruary 3, 2026 at 7:41 PM

    This post is an excellent technical reference for SharePoint administrators, providing much-needed clarity on the specific mapped and crawled properties required to manage URL fields effectively! Highlighting the relationship between crawled properties like ows_URL and their corresponding managed properties is vital for ensuring that search results and data queries remain accurate. I especially liked the straightforward breakdown of how to configure these settings to ensure seamless data retrieval across the platform. Just as precise technical configurations ensure a reliable digital infrastructure, specialized medical expertise is vital for health, which is what we prioritize at our Multispeciality Hospital in Kadapa. Thanks for sharing these valuable SharePoint and search optimization insights!

    ReplyDelete

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...
Read more

OverTheWire[.com] Bandit Walkthrough - JUST HINT, NO SPOILERS

overthewire bandit walkthrough - JUST HINT, NO SPOILERS, just all the hints you need. I made this walkthrough for people like me, i needed some help here and there, but didnt want the spoiler, and even some blogs like  https://www.yalpski.net/  (mentioned with appreciation) that have the solution collapsed, there is no help if i dont know what to do, just need some pointers. so lets go game portal is http://overthewire.org/wargames/bandit/ Bandit The bandit  game is mostly introduction to ssh, bash shell and their tricks Pre Level 0: Connect to SSH If you use linux, your command is " ssh " and thats it. For windows you'll need to download a software, it's in the Level 0 hints  (wikihow) eventually you need to learn more about the ssh command, but the basic is that connection is defined as " ssh <user>@<domain> -p <port> " CTRL+C to break process, CTRL+D to exit from current user's shell I wrote this one down since i co...
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab...
Read more