search

MscrmTools / MsCrmTools.SolutionComponentsMover

Transfer solution components across solutions
GNU General Public License v3.0
4 stars 5 forks source link

Include the Default solution as a source solution? #11

Open simes1 opened 3 years ago

simes1 commented 3 years ago

Now we can no longer export the Default solution it's really hard to compare customisations between two environments or discover unmanaged customisations not in any other solution.

Would it be possible to include the Default solution in the list of solutions available to copy from (perhaps with an "are you really sure?" if you select it...)

-- Simon

MscrmTools commented 3 years ago

Not sure that would be usable from a performance point of view. Copying ALL components will take time... There are other tools in XrmToolBox to compare environments customizations. You should better look in this direction

simes1 commented 3 years ago

I would I imagine that would take a while but so do other options I think (hence the need for a warning - or I suppose a filter/way to split into multiple target solutions). I tried using Solution Layer Removal to list out components with unmanaged customisations - it took ages, and seemed to miss quite a bit (The solution components that were included implicitly by virtue of the entity being set to include all entity assets - I think...)

I've looked at some of the XrmTB comparison tools before and used System Customisation Comparer (also takes quite a while to run). Unfortunately there is a lot of noise when comparing solutions (e.g. rarely does one have identical version numbers from the zillion hidden solutions in each environment) I find it easier to eliminate the noise quickly by comparing the unpacked solution XML files - with System Customisation Comparer one has to navigate down a complicated hierarchy for each difference to see if it's trivial or not and there is little/no filtering available.

However, there are a few more comparison tools listed now that I don't have installed so I will look at those too. It is frustrating that the default solution can no longer be exported - unpacking this is how I've managed to do this task in the past.

cookyrag commented 3 years ago

I would also like to see this feature, its also nice to be able to export the whole solution for backup purposes as well , if we could copy the default solution to a "backup" solution and then export you have a complete copy of all customisations

simes1 commented 3 years ago

I'm guessing that the reason we can no longer export the Default solution is that it's got so enormous that it won't export without erroring? I never found a way to do what I was trying to do. Another approach would be a way to copy everything in the unmanaged layer (fully segmented) into a solution. Before someone asks the solution components in the special Active solution do not comprise everything in the unmanaged layer - just some of them - I have no idea why...)