Warning: referenced component could not be found

[sunjuan1409]

Besides the 'Microsoft.ServiceBus' that's been reported in a previous issue I also get similar messages on the following components:

• 'Microsoft.Cloud.InstrumentationFramework.Events'
• 'Microsoft.Cloud.InstrumentationFramework.Health'
• 'Microsoft.Cloud.InstrumentationFramework.Metrics'
• 'Telerik.Web.UI'
• 'AuthorizeNet'
• 'AuthorizeNet.Helpers'

Projects: Adxstudio.Xrm and MasterPortal

[amervitz]

We'll have to decide whether to continue referencing these assemblies. They weren't provided by Microsoft.

The Microsoft.Cloud.InstrumentationFramework.* references come from a Microsoft.Cloud.InstrumentationFramework NuGet package that isn't publicly available and is likely an internal package used by Microsoft for their SaaS hosting. Here are some options I've thought of where we could go forward with this:

• Keep the references and live with the warnings. It might be informative for people to see the code Microsoft uses as a multi-tenant hosting provider, but it wouldn't be used or tested.
• Remove the references and all code related to them.

The Telerik.Web.UI references are to assemblies not included in DllImports, and is a commercial library that Microsoft appears to be using in their SaaS hosting for captcha purposes. Here are some options I've thought of where we could go forward with this:

• Keep the references and live with the warnings. Users could purchase the license for their individual use if wanting to be compatible with the features in Microsoft's SaaS hosting, but would not receive community support unless other community members are also using this commercially obtained library and choose to help.
• Find a free alternative version such as reCAPTCHA which had previously been used in Adxstudio Portals, but would result in a different user experience when moving to Microsoft's SaaS hosting.
• Remove the references and all code related to them.

The AuthorizeNet references are to assemblies not included in DllImports, and is for payment functionality Microsoft has removed in their SaaS hosting. Here are some options I've thought of where we could go forward with this:

• Keep the references and live with the warnings. The project would continue to exclude these assemblies to remain compatible with the features in Microsoft's SaaS hosting. It might be informative for people to see the code as a reference for implementing payment functionality but it wouldn't be used or tested. Users could obtain the libraries for their individual use if desired but would not receive community support unless other community members are also using this library and choose to help.
• Remove the references and all code related to them.

Feedback or other ideas on how to move forward on these is welcome.

[amervitz]

Closing this issue due to inactivity. Individual items will be addressed as needed in the future.

[rgsiiiya]

Note that both AuthorizeNet and AuthorizeNet.Helpers have nuget packages that can be imported which will clear those warnings.