index > ClickOnce and Setup & Deployment Projects > Microsoft .NET Framework Setup appears when trying to launch application

Microsoft .NET Framework Setup appears when trying to launch application

We have some new development machines which are running Vista SP1 and when trying to launch a click once application over http we get the .NET Framework Setup dialog asking if we'd like to install the Framework. I've actually gone with this and allowed to to repair the existing Framework installation but it makes no difference.

Can't seem to find a great deal out there on this problem. Strangely out of the new developer machines here only two have this problem, the third can launch the app flawlessly. They are all the same spec but obviously we've performed updates and installations slightly differently on the machines for this to occur.

If anyone has any suggestions as to what we might try in order to resolve this please let me know.

Matt_S_ Wednesday, May 13, 2009 9:13 AM

I'm able to get through with the problem. I found that DNS entries in the system were all messed up. Giving the correct DNS entries and system restart worked for me. By checking in the event logs I found that Kerberos was unable to create trust relationship with the domain. It is nothing to do with the .NET framework installation.

Anyways, thanks guys!

Thanks.
Adeel

Marked As Answer byRobinDotNetMVP, ModeratorWednesday, September 02, 2009 7:49 AM

adeeltaseer Wednesday, September 02, 2009 1:59 AM

How are they trying to launch the application? Have they already installed it, and it happens when they try to run it a second time, or have they never run it successfully?

RobinDotNet

Click here to visit my ClickOnce blog!

RobinDotNet Wednesday, May 13, 2009 10:53 PM

Noclick-once applications have been previously installed on the new machines - it's the first time we've tried to install on these. The apps are hosted ona webserver.

This is the same whichever click-once app we try (live, internal/testing). We've never seen this problem before with our deployments.

Matt_S_ Thursday, May 14, 2009 8:27 AM

Hi Matt_S_,

What's the operating systems of those machines do not have problems use? Do they use Vista also? How about uninstalling the .NET Framework totally, and reinstalling .NET Framework 3.5 SP1?

Best regards,
Bruce Zhou

Please mark the replies as answers if they help and unmark if they don't.

Bruce.Zhou Friday, May 15, 2009 8:56 AM

You must be specifying some version of the .Net framework as a prerequisite. Which is it, and which does your application target? The only cases I've seen this happening are these:

1) You have Vista (.Net 3.0 comes with it) and are targeting .Net 3.5 but aren't deploying it as a prerequisite and the doesn't have it installed. Although I have to say, I've never seen a CLickOnce deployment try to install .Net unless it's being deployed as a prerequisite. Except that GoToMeeting seems to use ClickOnce, and one of my coworkers is always prompted to install .Net 2.0 when he uses it (and he has .Net 3.5 sp-1 installed).

2) The .Net Framework installed on the computer is corrupted. Try doing a repair or an uninstall/reinstall.

3) Your application targets .Net 3.5 but your prerequisite is .Net 2.0 (I think ClickOnce is smarter than this, but mention it just in case).

We need more information, please.

RobinDotNet

Click here to visit my ClickOnce blog!

RobinDotNet Saturday, May 16, 2009 5:49 PM

We are having the same problem but for only one user accounts. For other accounts it is working fine. Another thing is can you try to open same Click One App from different machine other than the one it is installed.

Thanks.
Adeel

adeeltaseer Monday, August 31, 2009 3:19 PM

For the machine where you're having problems, if you set up a new user account does it have the same problem? If it does (I'd be surprised), can you set up the user who's having a problem with an account on a machine that doesn't have the problem and try it? (If that doesn't work, I'd be surprised).

I'm sure this is something to do with the machine itself. Have you tried uninstalling the .Net framework and reinstalling it? What version of .Net are you targeting, and what version is it trying to install?

RobinDotNet

Click here to visit my ClickOnce blog!

RobinDotNet Tuesday, September 01, 2009 3:10 AM

"For the machine where you're having problems, if you set up a new user account does it have the same problem?". I'll try and post the results in the forum.

About the second part: I did setup the user who's having a problem with an account on a machine that doesn't have the problem. It didn't work there as well. So, I believe that part of the problem is his User Account.

I don't think that it is something to do with the machine itself but I may be wrong, and have tried uninstalling .NET framework. It's 3.5 and its asking for same.

Any other ideas?

Thanks,
Adeel

adeeltaseer Tuesday, September 01, 2009 5:14 AM

If it is arepair there will be event log entries, category MsiInstaller describing what's missing. MSI setups are self-healing, the framework setup is MSI based, so it thinks something in the framework is incorrect and it's repairing it.

Make sure that nothing you're doing is replacing something that is part of the .NET framework.

Phil Wilson

PhilWilson Tuesday, September 01, 2009 8:25 PM

It doesn't make sense that the user would have the same problem on another machine. I'm assuming you picked a machine that someone else's account actually works on?

I'm re-reading the thread. Is this happening when the user actually runs the application from the start menu? Or does it happen when he tries to install it? If you dig down into the deployment folders and double-click on the exe file, what happens?

RobinDotNet

Click here to visit my ClickOnce blog!

Marked As Answer byRobinDotNetMVP, ModeratorWednesday, September 02, 2009 7:48 AM
Unmarked As Answer byRobinDotNetMVP, ModeratorWednesday, September 02, 2009 7:49 AM

RobinDotNet Wednesday, September 02, 2009 12:07 AM