Windows installer error

When i install my wpf installer while getting error like this. any body know about this issue.

Question :-

Error 1001. Unable to get installer types in the C:\\YM\ConfigUI\ConfigUI.exe assembly. --> Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

 The description for Event ID 11001 from source MsiInstaller cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

 If the event originated on another computer, the display information had to be saved with the event.

 The following information was included with the event: Product: YottaMark Case Labeling Solution -- Error 1001. Error 1001. Unable to get installer types in the C:\YM\ConfigUI\ConfigUI.exe assembly. --> Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
(NULL)
(NULL)
 (NULL)
(NULL)
(NULL)
 the message resource is present but the message is not found in the string/message table

Answer : -

Based on the error message in your second comment, it appears that your ConfigUI.exe assembly has been added as a Custom Action with the InstallerClass property set to true, but either no installer classes could be found in the exe or the exe could not be loaded due to missing dependencies.

You can see the list of Custom Actions by right-clicking on the installer project, selecting View and then Custom Actions.

If your exe does not can an installer class, then you can remove it from the list of custom actions.

If it does contain an installer class, then the issue is going to be missing dependencies. If fuslogvw doesn't work for you (it has always helped resolve this kind of issue for us), you can carefully review the list of references in the exe's project and compare them to what is listed in the installer project.

The other trick that we use is to examine the install directory while the error message is displayed on the screen. We can often see that DLLs are missing by doing this, usually because the path was entered incorrectly in the DLL entry within the installer project or because a condition was set incorrectly.