Crystal Reports UFL DLL limitation?

Question

Hello there,
Is there any kind of limitation on UFL Dlls that are being used on crystal reports? Such as connecting to webservices or using sql connections to reach data from databases or using 3rd party dlls?
the UFL dll is working fine, once i started debuging it i noticed that i could not call the webservice, not even create an instance of the SoapClient.
I did test the SoapClient from an Exe and it did work fine, just not inside this dll.
I did try to add
<system.net>
    <settings>
      <httpWebRequest useUnsafeHeaderParsing = "true" />
    </settings>
  </system.net>
to the app.config but still, no luck.
Any tips?

Answer 1

hello there,
I have tested in C#.net 2010 and vb.2010. Both gave me the same problem.
I did try the dll in 64 and 32 bit. Both seems to have the same issue.
I don't think that the problem is related with the webservice itself as i also have problems when i use other 3rd party dlls and apparently i can't/not be able to.
The DLL have been registered by visual studio after compiling (i did try to regasm it manually and did try debug mode too).
i did attach the dll to a process that will call the crystal reports map and the function that the map prints can't create an instance of the webservice soapclient.