The error "lc.exe has exited. The code is-1"

when the program is scheduled this day, the current compilation cannot be completed. The error is that lc.exe has exited, the Code is-1.
I checked it online because the third-party component developer express v2011 is used in the project. Share the following:
this third-party component is a commercial component, the main class of the component defines the attribute licenseprovider (typeof (licfilelicenseprovider.
when vs detects this class during compilation, it will check that the component uses the licfilelicenseprovider attribute, indicates that a component saves the license information in license. in the licx file, this file is saved in the properties folder of Solution Explorer in.
the content of this file is actually a reference. It stores the namespace, class name, file name, culture, and publickeytoken information of the main class used by the third-party component you are using, this file is automatically generated.
if this information does not match the internal content of the dll, lc.exe will display this error message. The reason for this information is that you used the beta version of the commercial component in the project, and the cracked version of the commercial component used during the release. When most commercial components are cracked, the strong name signature will disappear, so the cracked components are completely different from the reference information of the original test component. Therefore, during each compilation, Vs will call LC (license compiler) before automatically calling the language compiler, and a-1 error will occur.

Solution:
1. Delete the license. licx in the properties file and recompile it.
2. If this problem persists, you must use lidism to translate your cracked version into the Il language, and then use ilasm to re-compile it into a DLL, add/Key = [your strong name file] during compilation. add a strong name signature to the SNK parameter and use vs to re-compile it.

 Note: I also deleted the license under the properties file. licx, compilation, and the problem persists. Later, the license is displayed under the properties extension in solution resource manager on the development project interface. delete licx and recompile it.