It's possible that the signature app is using ASP.NET, either for web forms or web services. It could be that the default web stuff has been changed from 1.1 to 2.0 by your installer and your customer simply needs to get into IIS and set it back to 1.1 for whatever virtual directories are used by the signature app.

~~Bonnie




>>>I have a customer with a tablet PC. The customer is running an application that requires .NET 1.1, it is a signature application.
>>>The customer wants to install my application. My application requires .NET 2.0.
>>>My installer installs .NET 2.0 if it is not installed before installing my application.
>>>After my application is installed the signature application (that requires .NET 1.1) does not work anymore.
>>>If the customer uninstalls .NET 2.0 the signature application works again.
>>>
>>>I thought .NET 1.1 and .NET 2.0 could live side by side.
>>>My app is a winforms app, but I don't know if the signature app is winforms or asp.net.
>>>
>>>Any ideas?
>>>
>>>Thanks,
>>>Einar
>>
>>I have no problems with 1.1 and 2.0 side by side. When you say the signature application doesn't work, is there an error?
>
>The customer didn't mention anything about any error message, he just said the signature application didn't work. I called the customer back and left him a message asking if there was an error message.
>
>I tried to explain the best I could that my app is using the newer (of the two) framework and that the people that gave him the signature application should upgrade their application.