Open Zerajima opened 4 months ago
Would love to see this get fixed. We are so close to Plugin Packages being the savior we've all wanted. It's disappointing that the build/ALM processes we need don't support them.
Colleagues, any update regarding this topic ? I have faced exactly the same issue.
same here...
Colleagues, Actually, I have found the flow how to overcome the issue.
The guy on video shows the steps. https://www.youtube.com/watch?v=wzHLWNWcY2Q
I have tested and it works.
I have a Dataverse solution project (.cdsproj) which contains a single plugin package. The plugin is packed as nuget package, not as standalone assembly. If there is no relation between .cdsproj project and .csproj project of plugin, build works correctly, but it means I have to keep .nupkg file within the solution project folder. I wanted to avoid doing that, so I added a reference between Dataverse solution and plugin projects using "pac solution add-reference" command. After doing that and running "pac solution sync" command, the .nupkg file is removed from solution folder, but the build of the solution project does not work any more. The following error is thrown:
2>Microsoft.PowerApps.MSBuild.Solution.targets(102,5): Error : Unable to find assembly registration configuration for C:\_dev\DocentricCRM\src\Backend\Plugins\Docentric.CRM.Plugins\bin\Debug\net462\Docentric.CRM.Plugins.dll in the destination: obj\Debug\Metadata\PluginAssemblies.
I assume this does not work, because I'm packing the plugin assembly to nuget package, but it's only looking for the plugin assembly itself. All the examples of doing this, I could find, were done with standalone assemblies.
Is this a known issue? Is there some workaround I could use?