Open timomta opened 2 years ago
Hi @timomta - Thanks for bringing this up - I'm marking this as a future enhancement. Today the checks are all based on IIS configuration not runtime direct behavior/connections so this is a class of reference that might not be detected (also things like dependency on custom GAC'd assemblies).
Migration Assistant Did Not Catch COM object
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Customer's web site was a .Net 4.8 asmx site, but it also referenced the ADODB COM object. An example of this object can be found in Visual Studio 2019 here C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\adodb.dll
Expected behavior
Expected the tool to catch the COM object reference and provide an error in the Assessment Report.
Actual behavior
The tool provided a fully 'green' report for the site. We tried to migrate the site to Azure, but it failed to run because the inclusion of COM objects is not supported by the App Service.
Known workarounds
Provide a description of any known workarounds.