“Lc.exe "has exited and the code is-1 Solution

A third-party component is used today. After the component is deleted, "lc.exe" is exited,Code-1 error. I looked around, found the solution, and pasted it --

Possible cause: a third-party component is referenced in your project, and this third-party component is a commercial component. It defines licenseprovider (typeof (licfilelicenseprovider) in the main usage class of the component ))
This attribute.

When vs2005 detects this class during compilation, it will check that the component uses the licfilelicenseprovider attribute, indicating that a component uses to save license auxiliary information in license. in the licx file, this file is saved in the my project folder in Solution Explorer in vs2005.
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 your third-party component, this file is automatically generated.
If this information does not match the internal content of the dll, lc.exe will see 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, vs2005 will call LC (license compiler) before automatically calling the language compiler, and a-1 error will occur.

The solution is to set the license under the my project file. licx (if not visible, click the show all files option above solution) to delete and recompile. If this problem persists, which component of your cracked version must use lidism to translate it into the Il language, then use ilasm to re-compile it into a DLL, and add/Key = [your strong name file] during compilation. add a strong name signature to the SNK parameter and use vs2005 to re-compile it.

After a third-party component is used today, "lc.exe" exits and the code is-1. I looked around, found the solution, and pasted it --

Possible cause: a third-party component is referenced in your project, and this third-party component is a commercial component. It defines licenseprovider (typeof (licfilelicenseprovider) in the main usage class of the component ))
This attribute.

When vs2005 detects this class during compilation, it will check that the component uses the licfilelicenseprovider attribute, indicating that a component uses to save license auxiliary information in license. in the licx file, this file is saved in the my project folder in Solution Explorer in vs2005.
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 your third-party component, this file is automatically generated.
If this information does not match the internal content of the dll, lc.exe will see 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, vs2005 will call LC (license compiler) before automatically calling the language compiler, and a-1 error will occur.

The solution is to set the license under the my project file. licx (if not visible, click the show all files option above solution) to delete and recompile. If this problem persists, which component of your cracked version must use lidism to translate it into the Il language, then use ilasm to re-compile it into a DLL, and add/Key = [your strong name file] during compilation. add a strong name signature to the SNK parameter and use vs2005 to re-compile it.