CAS with .NET 2.0 and 1.1
-
Hi folks! Usually you'd expect that .NET 2.0 and 1.1 wouldn't influence each other, wouldn't you? This bug occurred after creating a mixed mode DLL on a computer with only .NET 1.1 installed. Because the application loading this DLL resided on a network drive and the DLL required some permissions usually not granted for intranet zone code, you had to adjust the CAS settings for the intranet zone (using the tools provided with .NET 1.1). After the DLL was installed on a customer PC (and the .NET 1.1 security settings were adjusted accordingly), the initialization of the DLL failed with some obscure security related exceptions and initially we didn't know why. Later on I found out that the customer's PC had .NET 1.1 installed as well as .NET 2.0. Only after adjusting the CAS settings for .NET 2.0 (!) would the DLL be initialized correctly. The 1.1 settings weren't taken into account at all! :doh: SO if you run into a similar problem, check if there are different framework versions installed...
Regards, mav -- Black holes are the places where God divided by 0...