Closed arp-mbender closed 3 months ago
PS. I've also tried to use the instrument
command, but this seems to not detect any plugins at all...
Downloading Plugin/Workflow Activity Metadata
Searching for classes in 'C:\MySuperSecretProject'
0 classes decorated with deployment attributes!
The folder path is correct - it contains all the .cs
currently deployed to CRM.
OK, I've delved into the codebase. It seems that SPKL isn't the right tool for the job. It just cannot do what I want it to do.
As far as I understand the flag
/e
should do what I'm looking to do: only updates the DLL in CRM, without registering any new steps. I'd like to make use of this on plugins that have not, at the time of writing, been in any way prepared for SPKL (i.e. they have no attributes added, which would direct the registration process).In other words, all I want is for SPKL to update the DLL in CRM.
However running the operation
spkl plugins spkl.json /e
(where the JSON file has the expected solution + DLL file path) results in very lacklustre logs and... seemingly nothing has changed, CRM side.That's it, no other logs are being generated, and the DLL seems to be unchanged in CRM.
What am I doing wrong? Or is SPKL not capable of updating the binaries in CRM until the codebase is expanded with the required attributes, even with the
/e
flag?