🚀 go-pugleaf

Environment:
- .Net Framework v2.0.50727
- Borland C++ Builder 5

We are extending our C++ application with functionality in a C# dll.
The C++ app creates an object from the (registered) dll and calls a
method in it. This method creates and uses an XslCompiledTransform
object. Unfortunately, when calling Load() on this object, the
application crashes with an access violation in the .Net runtime. This
problem does not occur when we call the same method from a VB
application, nor does it occur when performing the same steps from
within a (C++ Builder) console application. Until now, we've only
managed to reproduce the problem from within a windowed (VCL)
application.

Does someone have any clue about what might cause this problem, and
moreover, what can be done about it?
TIA,
Jeroen


The smallest example that exhibits the problem contains:

* The C# file issue.cs (compile with csc /target:library issue.cs, and
then register it with regasm /codebase issue.dll)
---
using System.Runtime.InteropServices;
using System.Xml.Xsl;

[Guid("694C1820-04B6-4988-928F-FD858B95C880")]
public interface IIssue
{
  void issue ();
}

[Guid("9E5E5FB2-219D-4ee7-AB27-E4DBED8E123E"),
 ClassInterface(ClassInterfaceType.None)]
public class Issue : IIssue
{
  public void issue ()
  {
    XslCompiledTransform transformer = new XslCompiledTransform ();
    transformer.Load (@"c:\transform.xsl");
  }
}
---

* The xsl file c:\transform.xsl:
---
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0"
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
</xsl:template>
</xsl:stylesheet>
---

and
* The C++ Builder program (project2.cpp in project2)
---
# include <olectnrs.hpp>
USERES("Project2.res");

WINAPI WinMain(HINSTANCE, HINSTANCE, LPSTR, int)
{
  OleInitialize (0);
  Variant obj = CreateOleObject ("Issue");
  obj.OleFunction ("issue");
  return 0;
  // Cut away the from creation and message
  //loop - not needed for example
}
---