One of my colleagues faced a situation where he had installed a plugin assembly into database but was not able to locate its DLL, and now he wanted to deploy it in some other server.
In MSCRM all plugins related information like its name, content, createdBy, createdOn. ModifiedBy, ModifiedOn etc store in PluginAssemblybase Table. You can get it by below Query result :
select * from PluginAssemblyBase
Below are some column description of PluginBaseTable :
In MSCRM all plugins related information like its name, content, createdBy, createdOn. ModifiedBy, ModifiedOn etc store in PluginAssemblybase Table. You can get it by below Query result :
select * from PluginAssemblyBase
Below are some column description of PluginBaseTable :
Column Name
|
Description
|
Name
|
Store name of Plugin
|
Source Type
|
Where the Plugin registered
0 - Database
1 - Disk
2 - GAC
|
content
|
Store content of DLL
|
These are the steps to get DLL from Content :
Get the encoded base 64 string representation of the plugin from PluginAssemblyBase table.
select name,content,*
from PluginAssemblyBase
Use that content and get the dll from the following site.
Set decode and export to binary file option there with filename having extension as .dll
Open the dll in the reflector tool and use the source code to build that assembly.
Special thanks to (hackingsetting50@gmail.com) for exposing my cheating husband. Right with me i got a lot of evidences and proofs that shows that my husband is a fuck boy and as well a cheater ranging from his text messages, call logs, whats-app messages, deleted messages and many more, All thanks to
ReplyDelete(hackingsetting50@gmail.com), if not for him i will never know what has been going on for a long time.
Contact him now and thank me later.