Has VS 2010 SP1 changed where the .config file is picked up from in VSTO add ins?

I have an outlook 2010 add-in that has a service reference to a simple web service we have set up. The config for the service is in the app.config file. This add-in is deployed using windows installer into the program files folder.

This has been working without a problem until yesterday.

Yesterday I installed VS 2010 SP1 and now when the add-in tries to access the web service it has the error "Could not find default endpoint element that references contract in the Servi开发者_如何转开发ceModel client configuration section."

Does anyone know what has changed and what is causing this problem?

If I open the project in VS, build and then run from within VS the config is picked up fine.

Thanks Gavin

---

The actual solution is more simple. There was a breaking change made to VSTO 4 sp1 in that the manifest has to be a fully qualified URI. So when building your setup project, you must prefix the path to the manifest with file:/// and everything works as you'd expect again. They didn't get the documentation and tutorial pages updated in time for the release. I'm not sure that they have been yet.

---

Perhaps you're hitting a problem with extensionless services after installing SP1? http://support.microsoft.com/kb/2468871 - Issue 16?

---

I had this exact same problem. After installing Visual Studio sp1 (which installs VSTO 4 sp1), my Outlook addin could no longer find its config file for service endpoints. The only solution I've found so far is to run the VSTO setup (the new one) and choose uninstall, then run the old version that was previously installed and rebuild the setup package. If the new version is installed on the client machine, that machine will have this issue. Your setup may not detect it because typically you specify a minimum version for it to look for. I haven't found any other info about others having this problem besides yourself or anything official from MS about the problem.