Hi all
ReportListeners.H contains (amongst many others) the following DEFINEs #DEFINE OUTPUTXML_DOMFREETHREADED_DOCUMENTOBJECT "Msxml2.FreeThreadedDOMDocument.4.0" #DEFINE OUTPUTXML_XSLT_PROCESSOROBJECT "Msxml2.XSLTemplate.4.0"
These are used/referenced in the following classes/methods In the HTMLListener class FillRunCollector In the XMLListener class FillRunCollector GetRunNodeContents BeforeReport ApplyXLST LoadProcessorObject GetVFPRDLContents AdjustXLSTParameter
MSXML4 is no longer supported and, apparently, has a security vulnerability. I have removed it from my system but I need to know if any of these methods will ever be invoked from/by our application. So far I have been unable to find under what circumstances one or more of these methods might be invoked.
Any ideas? Sample code?
BTW, having removed MSXML4, CreateObject("Msxml2.FreeThreadedDOMDocument.4.0") and CreateObject("Msxml2.XSLTemplate.4.0") both give a "Class not registered" error which I expected. I did wonder whether it would be safe to remove the .4.0 from the DEFINEs. Doing so _does_ allow me to create the objects without error.
Many thanks
Paul Newton
Expect slow replies from the US as today is a national holiday.
Are you using Report Listeners in your application?
You should be able to test this empirically: if you can run all the functions of your app with MSXML4 removed, you should be all set.
On Thu, Nov 24, 2016 at 6:13 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
Hi all
ReportListeners.H contains (amongst many others) the following DEFINEs #DEFINE OUTPUTXML_DOMFREETHREADED_DOCUMENTOBJECT "Msxml2.FreeThreadedDOMDocument.4.0" #DEFINE OUTPUTXML_XSLT_PROCESSOROBJECT "Msxml2.XSLTemplate.4.0"
These are used/referenced in the following classes/methods In the HTMLListener class FillRunCollector In the XMLListener class FillRunCollector GetRunNodeContents BeforeReport ApplyXLST LoadProcessorObject GetVFPRDLContents AdjustXLSTParameter
MSXML4 is no longer supported and, apparently, has a security vulnerability. I have removed it from my system but I need to know if any of these methods will ever be invoked from/by our application. So far I have been unable to find under what circumstances one or more of these methods might be invoked.
Any ideas? Sample code?
BTW, having removed MSXML4, CreateObject("Msxml2.FreeThreadedDOMDocument.4.0") and CreateObject("Msxml2.XSLTemplate.4.0") both give a "Class not registered" error which I expected. I did wonder whether it would be safe to remove the .4.0 from the DEFINEs. Doing so _does_ allow me to create the objects without error.
Many thanks
Paul Newton
[excessive quoting removed by server]
Thanks for your reply Ted. And according to the BBC "Footage has been captured in southern California of possibly the world's worst traffic jam during the great US Thanksgiving getaway."
Yes we are using Report Listeners.
My (empirical) testing so far has revealed no issues. But I have a further question - I have MSXML3 and MSXML6 installed and the following both work CreateObject("Msxml2.FreeThreadedDOMDocument.3.0") CreateObject("Msxml2.FreeThreadedDOMDocument.6.0") Whereas CreateObject("Msxml2.FreeThreadedDOMDocument.4.0") fails as one would expect. BUT if I use CreateObject("Msxml2.FreeThreadedDOMDocument") it works but how would I find out which version of MSXML the object has been created from?
Thanks again
Paul Newton
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: 24 November 2016 12:17 To: profoxtech@leafe.com Subject: Re: Report listeners and MSXML4
Expect slow replies from the US as today is a national holiday.
Are you using Report Listeners in your application?
You should be able to test this empirically: if you can run all the functions of your app with MSXML4 removed, you should be all set.
On Thu, Nov 24, 2016 at 6:13 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
Hi all
ReportListeners.H contains (amongst many others) the following DEFINEs #DEFINE OUTPUTXML_DOMFREETHREADED_DOCUMENTOBJECT "Msxml2.FreeThreadedDOMDocument.4.0" #DEFINE OUTPUTXML_XSLT_PROCESSOROBJECT "Msxml2.XSLTemplate.4.0"
These are used/referenced in the following classes/methods In the HTMLListener class FillRunCollector In the XMLListener class FillRunCollector GetRunNodeContents BeforeReport ApplyXLST LoadProcessorObject GetVFPRDLContents AdjustXLSTParameter
MSXML4 is no longer supported and, apparently, has a security vulnerability. I have removed it from my system but I need to know if any of these methods will ever be invoked from/by our application. So far I have been unable to find under what circumstances one or more of these methods might be invoked.
Any ideas? Sample code?
BTW, having removed MSXML4, CreateObject("Msxml2.FreeThreadedDOMDocument.4.0") and CreateObject("Msxml2.XSLTemplate.4.0") both give a "Class not registered" error which I expected. I did wonder whether it would be safe to remove the .4.0 from the DEFINEs. Doing so _does_ allow me to create the objects without error.
Many thanks
Paul Newton
[excessive quoting removed by server]
On Thu, Nov 24, 2016 at 7:38 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
Thanks for your reply Ted. And according to the BBC "Footage has been captured in southern California of possibly the world's worst traffic jam during the great US Thanksgiving getaway."
Yes, it was very pretty.
We're heading off in a few hours ourselves, passing through the bottleneck of Boston.
Yes we are using Report Listeners.
My (empirical) testing so far has revealed no issues. But I have a further question - I have MSXML3 and MSXML6 installed and the following both work CreateObject("Msxml2.FreeThreadedDOMDocument.3.0") CreateObject("Msxml2.FreeThreadedDOMDocument.6.0") Whereas CreateObject("Msxml2.FreeThreadedDOMDocument.4.0") fails as one would expect. BUT if I use CreateObject("Msxml2.FreeThreadedDOMDocument") it works but how would I find out which version of MSXML the object has been created from?
I can't tell you right off, but I'd see if I could explore the object heirarchy for a "Version" property. Alternatively, you can search the machine for msxml*.dll and similar names, and check Properties via Windows Explorer.