Message has been edited, click here to see original contentOriginal Message - [03/08/2012 - 01:21 PM]
I did have NET Framework 3.5 SP1 installed. When I was having this problem, I went direct to Microsoft and downloaded 3.5 SP1. But it didn't fix the problem.
Then, I noticed that they have a note on NET Framework 2.0 that says:
"Overview
The .NET Framework 2.0 Service Pack 2 provides cumulative roll-up updates for customer reported issues found after the release of the .NET Framework 2.0. In addition, this release provides performance improvements, and prerequisite feature support for the .NET Framework 3.5 Service Pack 1. "
So, it appears that net framework 2.0 had some requisite files even for 3.5 SP1.
I installed NET Framework 2.0 and the problem went away.
I did have NET Framework 3.5 SP1 installed. When I was having this problem, I went direct to Microsoft and downloaded 3.5 SP1. But it didn't fix the problem.
Then, I noticed that they have a note on NET Framework 2.0 that says:
"Overview
The .NET Framework 2.0 Service Pack 2 provides cumulative roll-up updates for customer reported issues found after the release of the .NET Framework 2.0. In addition, this release provides performance improvements,
and prerequisite feature support for the .NET Framework 3.5 Service Pack 1. "
So, it appears that net framework 2.0 had some requisite files even for 3.5 SP1.
I installed NET Framework 2.0 and the problem went away.
PS: There is also a note on NET Framework 2.0 that mentions something about a
FULL NET Framework 3.5 SP1. So it might be that an update to SP1 doesn't fix it but if you do a "full" install, it might. Haven't tested that. I'll leave it up to othrs. I just know that 2.0 does mention dependencies for 3.5.