I know that using custom actions written in C# is not a very good idea, but it
happened we are using it in our project.
I experience very exasperating problem with my dll. SOMETIMES, when I add new
custom action to my cs-file, some custom action that worked good previously
starts to return
Are you using P/Invoke (DllImportAttribute) for any custom actions? If the
referenced DLL is not available in the system PATH environment variable you
will see this. This is common for native debug builds, but for managed CAs
you shouldn't see this unless you're referencing an assembly that you're
2 matches
Mail list logo