BackgroundWorker does not start unless .NET 3.5 is installed on client computer

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • PhilY
    New Member
    • Feb 2008
    • 2

    BackgroundWorker does not start unless .NET 3.5 is installed on client computer

    Hello,

    I'll try to give what I think is sufficient and relevant information about my problem but feel free to ask questions if you need to know more to understand my problem.

    I have developed a .NET application using VS 2005 and the about dialog box tells me it's using .NET 2.0.xxx.xxxx. My app works great on my development box (WinXP SP2) and I do not have .NET3.5 installed. However when I run my same app on a test machine, also running WinXP SP2, the BackgroundWorke r never starts. I found this out by using a bunch of dialog boxes and GUI label changes - couldn't quite get remote debugging to work. The most strange thing is that when I install .NET run time 3.5 on the testing machine, things work. I have created an installation project via VS 2005 for my app and it detects .NET2.0 dependency and automatically installs .NET2.0 at install time. I have no evidence to believe that the automatic .NET installation doesn't work.

    I'd appreciate any ideas.
  • PhilY
    New Member
    • Feb 2008
    • 2

    #2
    Dependency walker tells me the same thing for my app whether I have .NET 2.0 or 3.5 installed so I don't think it's a dll issue.

    Comment

    Working...