Microsoft is about to release a .NET cross-platform plugin for web browsers (Windows and Mac, IE and Mozilla, etc.) called Silverlight. This is similar to Java applets, Adobe Flash, etc., and provides rich GUI capabilities in the browser.
The plugin provides its own - smaller - version of .NET 2.0/3.0, so applications built against it have to use a somewhat reduced set of framework libraries, and also permissions (sandbox). They must link against a separate set of assemblies, including the core assemblies (mscorlib.dll, system.dll).
Here is the problem I have: I had the idea that, instead of calling a web service from the Silverlight code (running in the browser), I would call an ICE service instead. However, icecs.dll is built against the standard .NET framework, so it won't work with the Silverlight framework. I am sure, most of the code for icecs.dll would compile against Silverlight OK, but there are a few areas that would not work, as they use the Windows API directly (the network layer, I think).
Has anyone any ideas on the subject?
It would be nice if ICE worked on a sandboxed CLR.
Karl

Reply With Quote