<snip>

>Seen from that perspective it might be arguable, whether I am allowed to run my own copy on linux. But if I sell an app with the runtimes, how am I to control where it is installed ? If it works, it works. Who is the person MS will be going after ? The developer usually has no right to enforce how customers install the product. The only bugout might be an EULA referring to the MS EULA and try to stay out of it...

I don't agree with that control by MS over where our apps are used but what can we really do about it. So we have to respect the contract.

There's one thing though. I think that MS should tell us how to protect ourselves. What I mean is that MS should tell us what to include in contracts when we sell our applications. If they want us to impose certain restrictions they should be the one responsible for the restrictions not us.

I don't want to hire lawyers just to be sure of what to add or not when I make contracts for customers.

That way it would be clear that the part added would be for MS to defend.

An example. I have a client thas uses my application and thinks it's so good that he installs it on Linux. In doing so he does'nt tell me but someone from MS finds out about it. In that case I could be the one sued by MS but I did'nt do anything wrong.

In my contract it could be specified what can and can't be done. This way if the client does something wrong I've got a protection because that client has been advised that MS will come after him not me.