Hi Big Cat, no nothing that exotic, for an HTTP Client I just have a simple synchronous JScript wrapper round MSXML2.XMLHTTP, for our purposes this is fine for testing our OSB Web Services. I have to be careful as we have a few non technical testers and I need to make it as easy as possible for them to write automated tests.
Saying that, it'd be pretty nice to write some sort of HTTP Client in .Net, then again, if I'm not careful I'd try and write everything in C#!
My Primary uses of the CLR Bridge are:
1. Accessing the WinSCP.dll class library to overcome Test Completes rather bizarre absence of FTP utils
2. A Class library for creating and looking after background processed because I hate using Sys.OleObject("WScript.Shell");
3. A bunch of helper functions, Test Complete doesn't expose the whole of .Net and there can be impedences mismatches at times so these overcome those sorts of things
Phil