Today, I met a wonderful problem. Although it has been solved, I still look confused. I’d like to present some solutions to it https://www.cnblogs.com/zwjaaron/archive/2012/06/08/2541430.html I solved it by referring to this article, but the problem is different
First, describe my problem
The release process of our project is to complete the local development, submit the test environment, complete the test, submit the business test environment, and finally go online. Previously on: our new version development has been completed, but the test time is abundant, so we have carried out the next iteration of development. As a serious developer, we have passed the self-test of the test environment. Then, the business test environment is submitted (the internal test needs to package the code and publish, while the business test environment directly and automatically deploys and publishes, which is different). After a small problem was changed in the super project that was originally running, (a reference was added), the local operation was successful, and the development test environment was broken. I didn’t believe it. At this time, my colleagues had released the business test environment. I went to the business test environment and tried it. There was no problem. I was angry and confused. I tried it again in the development test environment, but I was confused! What’s the reason?The first reaction is that it has not been published successfully. All kinds of deletion and republication will lead to a predictable and useless result! Unknowingly, two hours have passed, and the problem has not been solved. In my heart, I really want to develop for half an hour, and I doubt whether I am a serious developer when this problem is solved for two hours
Helpless, want to ask God help, but now God is very busy, how to do?Find Du Niang, and find an article about this problem, the only one (but very useful!). After reading the article, my understanding is that the reference plug-in changes, and the project reference between various projects will cause impact. You need to clean up all the solutions, regenerate them, and then publish them again. It seems that the problem can be solved. Give it a try. There’s no way out anyway. So, it started a long process of closing all projects, cleaning up solutions, regenerating solutions, republishing projects, and so on. No! Once more! Still no, in a rage, the plug-in has changed the project to delete, re download, and then clean up all solutions again, regenerate, re release, problem solving
Note: before deleting, don’t forget to back up or submit your modified information, otherwise, it will be miserable
To summarize the description of the problem: there is no problem running locally. After the release, the entity type XXX is not part of the model for the current context appears
Solution:
Delete, download, clean up all solutions again, rebuild and publish the changed plug-ins
Finally, although the problem has been solved, the specific reason is still confused. I always feel that this problem has been solved by mistake. OK, no matter what, I’m happy that it has been solved
Similar Posts:
- Error reporting life processing instructions for building spring boot project
- Git review :error: unpack failed: error Missing tree
- [Solved] Eclipse Run Web Error: Setting property ‘source’ to ‘org.eclipse.jst.jee.server
- SDK location not found. Define location with sdk.dir in the local.properties file or with an AND…
- undefined symbol: xxx – undefined reference to `typeinfo
- Some solutions to the problem of “web pack / lib / node / nodetemplugin” in the development of angular
- Error 500: javax. Servlet. ServletException: srve0207e: uncaught initialization
- Maven Error: Failed to execute goal on project xxx: Could not resolve dependencies for project
- The problem of JUnit test report class not found in maven
- Error reported under webuploader IE9 [How to Fix]