Problems installing TT09 due to .NET 3.5 SP1?

I ran into this posting on Aaron Stebner's Blob today. It caught my eye since I use TurboTax 2009. I haven't run into this problem myself, but with the number of folks out there who DO, I thought it might be helpful...

formatting link
Apparently, TT09 has some sort of verification tool to check that the correct version of .NET Framework is installed. It needs 3.5 SP1. It seems that in some cases, it reports the problem and suggests re-installing SP1. Sometimes this doesn't work.

Aaron's article gives a very nice description of what to do for various operating systems in the event this happens.

Reply to
Hank Arnold
Loading thread data ...

Hank Arnold wrote in news:4b614fc5$0$31268$ snipped-for-privacy@cv.net:

Thanks. Haven't had any TTax problems, but have seen numerous user problems where getting the proper .NET set up was a PITA. I don't think MS did a good job of integrating .NET into the OS (at least XP but I don't think vista/w7 is any better). Maybe this is a side effect from some of the anti-trust stuff that forces unbundling of OS features, but it is hard for users to authoritatively determine that .NET is properly installed on their system. The same goes for certain other OS features like MSXML.

scott s. .

Reply to
scott s.

just checked on my XP system - Control Panel - Add/Remove Programs and I have several versions installed....

1.1 2.0 sp2 3.0 sp2 3.5 sp1

Wonder if these are like Java - in that some apps "require" a specific version due to subtle differences in the API's and other module relationships ?

It would be nice to delete the older versions - but who knows what apps would break :(

Reply to
ps56k

"ps56k" wrote in news:hkfa14$nbe$1 @news.eternal-september.org:

authoritatively

All of the individual versions are needed.

.NET is much like JAVA, Programs need the Version of .NET that they use. Later versions do not replace earlier versions.

Reply to
CSM1

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.