Last post Dec 19, 2006 05:09 PM by mikebridge
May 09, 2006 03:34 PM|richbaker|LINK
May 09, 2006 06:10 PM|billhie|LINK
There is a known issue where you can get into this state if the settings.settings file ever gets deleted, or is missing, and dynamic urls are used. The fix is to open the Settings.settings file (just double-click it). You should see entries similar to the
following for you dynamic urls.
Name Type Scope Value
MyApp_localhost_Service (Web Service URL) User http://localhost:2305/WebSite8/Service.asmx
Notice the type field - it needs to be set to "(WebService URL)" - one of the choices in the type dropdown. Most likely it is set to be of type String and this what causes the error.
Can you try this? We are looking at getting this fixed for SP1 of Visual Studio (it is an issue in the core VS code base so WAP cannot fix it directly.)
May 09, 2006 08:53 PM|richbaker|LINK
May 09, 2006 10:36 PM|billhie|LINK
May 09, 2006 11:23 PM|BradleyB|LINK
btw: this post highlights some of the differences is proxy generation and web.config settings between VS03 WAP and Web Sites.
Hope this helps,
May 10, 2006 10:31 AM|richbaker|LINK
May 10, 2006 07:51 PM|billhie|LINK
May 10, 2006 08:40 PM|richbaker|LINK
May 10, 2006 10:03 PM|billhie|LINK
When you opened your settings file, did it tell you that new values from app.config (actually web.config) will be added? Try one more thing. Dynamic url information is stored in web.config as well. You will see an entry like the following:
Back up your web.config and then do the following:
1) Delete settings.settings
2) Open web.config and Delete the entry that look like: <section
3) Further down in the web.config you should will see the following, with one <Setting> per web reference. Remove all the web references from there.
May 11, 2006 09:29 AM|richbaker|LINK
May 11, 2006 04:38 PM|billhie|LINK
Do you see any of the application settings enties in web.config? Can you try backing up your web.config somewhere, and then delete the one in your project. Delete the settings.settings file as well. Now try updating your web references. Does this work? If
not, can you again delete web.config and the settiings file, and your web references, and then re-add those references?
I should have asked earlier, but which version of WAP do you have installed? You can check the version using help\about and selecting Web Applicaton projects - it will be displayed in the details section. Is it the latest (Version 8.0.60501.00)?
May 11, 2006 05:19 PM|richbaker|LINK
"The custom tool 'MSDiscoCodeGenerator' failed. Object reference not set to an instance of an object."
May 11, 2006 05:47 PM|billhie|LINK
Your version number is correct (I was looking the build just prior to the release). I am pretty much out of ideas. I can't explain why it would work in a new web and not in your other web. Can you try one more thing? Add a new WAP project to your solution
and add the web references. Now copy the web.config and settings files from this new project to your existing project (just drag n drop them in the solution explorer). Now try updating your web references in the existing web (or better yet remove them first
before adding the web.config and settings file). Does this work?
May 11, 2006 09:09 PM|richbaker|LINK
May 12, 2006 12:39 PM|richbaker|LINK
May 12, 2006 05:04 PM|billhie|LINK
May 12, 2006 05:05 PM|billhie|LINK
May 12, 2006 07:26 PM|billhie|LINK
Jul 26, 2006 07:08 PM|jcnovoa|LINK
Dec 19, 2006 05:09 PM|mikebridge|LINK
Was there a fix for this? I stepped through all the suggestions here and still can't re-import my WSDL file.