Problem:
During programming, I call the dynamic link library statically in ocx, And the link prompts error: Project: Error prj0050: failed to register the output. Please try to enable "redirection for each user", or register this component from the command prompt window with the elevation of privilege. I thought it was a permission issue in win7. Can I check the attributes?
Answer:
According to the description, it is certainly not a permission issue, but because the DLL referenced in OCX is not placed in the directory where the OCX control is generated, and the link will not be found.
The query information is as follows:
[C ++] "Project: Error prj0050: failed to register output. Make sure that you have the permission to modify the registry.
Original space, software technology, computers and networks
Yan hongrui published on 19:49:39
Use VS 2005 to write the OCX control. It is a good word. If project: Error prj0050: the output cannot be registered. Make sure that you have the permission to modify the registry.
After reading it for a long time, I am an administrator and cannot delete debug. Project: Error prj0050: failed to register output. Please ensure you have the appropriate permissions to modify the registry is really troublesome.
I had to consider the changes step by step and found that a DLL was called. This lib has already been # pragma comment (Lib, "tmdapi. lib"). just delete the DLL call and consider it. You just have to move the DLL cpoy to the output directory. All third-party DLL files are put together and then registered.
In the current directory, % WINDIR % and % Windir % \ system32 are all supported.
Microsoft is also harmful.
Http://msdn2.microsoft.com/en-us/library/ms235584 (vs.80). aspx
Project Build error prj0050
Error Message
Failed to register output. Please ensure you have the appropriate permissions to modify the registry.
The Visual C ++ build system was not able to register the output of the build (DLL or. EXE). You need to be logged on as an administrator to modify the registry.
If you are building a. dll, you can try to register the. dll manually using regsvr32.exe, this shoshould display information about why the build failed.
If you are not building a. dll, look at the build log for the command that causes an error.
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/qinlicang/archive/2009/07/02/4315318.aspx
Javascript calls ActiveX objects
Http://www.csharpwin.com/dotnetspace/10222r1592.shtml