Community
Participate
Working Groups
Currently, ECF is deployed via a small number of features via an update site. For consumers that wish to use only a subset of ECF APIs (e.g. discovery, remote services, docshare, file transfer, others) this structure is too coarse. Smaller and more-easily consumable IUs should be created/deployed via P2.
REsolving as fixed for 3.0.0