Oleg,

> It should work fine.

Have you red the knowledge base article:
815112 INFO: Use of MSXML is Not Supported in .NET Applications
http://support.microsoft.com/default.aspx?scid=kb;en-us;815112

It states: "Using MSXML in .NET applications through COM interoperability 
can result in unexpected and problems that are difficult to debug."

If I undertand the article, it means "it will not work fine". I am trying to 
find out what can go wrong.

Thanks for the response,
  Matej

"Oleg Tkachenko [MVP]" wrote:

> Matej Trampus wrote:
> 
> > I am in working in C#. Are there any problems if I us COM component, that 
> > internaly uses MSXML, but does *not* expose MSXML objects.
> 
> I don't think there are any problem if you have to use this component - 
> that's what interop was designed for.
> 
> > 2. What can happen if COM componente returns pointer to MSXML object 
> > (IXMLDOMNode etc). What are the symptoms? Can the whole application domain 
> > crash. Can I get wrong results?  Are there memory leaks,... Does this only 
> > happens in ASP. NET applications,...
> 
> It should work fine. But it's still introp and if there will be any 
> interop problems you could get an answer like "use System.Xml instead of 
> MSXML".
> 
> -- 
> Oleg Tkachenko [XML MVP]
> http://blog.tkachenko.com
>