Blogging the Interop blogs -Framework versions; APIs evolve; Jagged arrays

. NET Framework version issues
Recently, U.K. developer Chris Alcock wrote about good API Design. A key point: you should never make changes to the API that will break your client’s code. An example cited: throwing exceptions based on values previously considered ok.

Even more recently, Alcock came across the precise problem. It occurred while installing  the .NET 2.0 Runtime on a server that in turn runs a number of .NET 1.1 applications and a number of classic ASP applications consuming COM components written in .NET 1.1.

Investigation revealed that instead of using the .NET 1.1 version of System.Web both CScript and the IIS DLLHost were loading the .NET 2.0 version. Loading the source code for the component into Visual Studio 2005 and attempting to compile and run a simple test application revealed a Null Reference Exception from within the framework.

“A code change to use a call to System.Web.HttpRuntime.Cache to obtain the cache instance fixed our problem, and a quick rebuild of the component against .NET 2 and redeploy to the server and we were back up and running,” wrote Alcock.

Commenting on Alcock’s blog, well-known developer-blogger Scott Hanselman noted a way to force IIS to use a specific version of the framework.

When APIs Evolve or- How I Lost My Lunchtime -
Good API design –
How to Force IIS to Load a Certain CLR -

History of Office XML formats
Brian Jones has created a timeline depicting the history of Office XML formats, beginning in 1998. He is open to additions. Take a look back in formats.

History of Office XML formats - MSDN Blog

Known-issue in WCF bungles bindings in WSDL
Ted Neward starts a trouble ticket rolling on Apache archives.

Working with WCF - Apache archives

Jagged arrays, and empty too
“Tiberiu” developed a Java web service which contains a simple function - the function returns a double-dimensional array of integers. The next step was to create a simple .NET web client which calls the function. But, when running a WSDL utility (generated by an Eclipse bottom-up web service wizard), “the result is returned as an empty jagged array”. Any vet SOAP serializers out there that can help?

WSDL question - Tech-Archive

Leave a Reply