Unable to manage different versions of dependent programs

[Sorah]

I recently purchased a PC especially for gaming, chatting, downloading movies and internet surfing. I have a package that relies on Microsoft .NET Framework 2.0 SP1, but I can’t do anything to manage the dependencies. As SP2 is the latest version of .NET 2.0 I would like have a policy known as Managed Software Delivery Policy that will automatically install SP2 if SP1 is not available. If I place it as reliant on .NET 2.0 SP1 then it will install .NET 2.0 SP1, but that has been outdated by .NET 2.0 SP2. If I place it as reliant on .NET 2.0 SP2 it will install SP2 even where it finds SP1, and I don't desire to do. If I modify the detection or applicability criteria for the SP2 Software Release then I require two different Software Releases for .NET 2.0 SP2. What is the best way to use 7.0 Managed Software Delivery Policy? Is anyone aware about such issues? If yes then please do the needful.

[Villiers]

The issue that you are facing is complicated. The issue that you have posted is quite new to me. You are the first person who is discussing such issues with me. I haven’t tried to do such things. I am not a software professional that can be the reason I am finding this issue complicated. I won’t be able to provide you the necessary suggestion that you need to overcome the issue. I will surely try to find the exact solution for that and will inform you about it. May be someone else can help you out this time.

[Ronchi]

The issue that you have posted is quite interesting. I will try my level best to help you out as much as I can. Many people had discussed such issues with me before but at that time I provided them the exact suggestions that they needed. To get rid from such issues I recommend you to include detection criteria for SP1 to the SP2 package. But doing that SP1 will assume that the endpoints meet the SP2 dependency. Only the detection rule for MSI product will do the task. Try it out and inform me about the experience.

[Dwarner]

After I read your post I came to know about your issue. According to me you will require a third-party software application for this task. If you want to view for minimum of SP1 but apply that SP2 is no available then you are not going to speak about neither SP1 software resource nor SP2 software resource. If the third party software application doesn’t find SP1 or SP2 then it would install SP2 package. I don’t have any reason to put an older version (SP1) in your environment. This was my opinion regarding your issue.

[Author]

I have previously solved many issues that were related to the issue that you have posted. As you are not having much knowledge about the issue that is the reason you are finding this issue more complicated. To solve the issue I would recommend you to check for .NET 2.0 any Service Pack in a software delivery policy. After that you can design a script that would verify for a file or reg key that is unique to both. If it finds none of them then you can direct it to the condition path to install SP2 or it can install as required. These are my suggestions for you to overcome the issue that you are currently facing.

[Sorah]

I am very grateful to you for all the suggestions and responses that you have given me to overcome my issue. Your recommendations helped me a lot. Previously I had discussed this issue with my colleagues but they could not help me to overcome the issue. You are the first person who supported and helped me. After reading all your post I will decide the correct procedure to overcome the issue. I will also see to it that I won’t face such issues in future.