Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Description of Problem:
The code completion window does not appear (automatically nor manually) when consuming a .NET 2.0 Web Service class. I haven't tried WCF as I don't have any to try.
Steps to reproduce the problem:
1. Add a Web Reference (.NET 2.0 framework).
2. Declare a variable to the web service and instantiate it.
3. Type the variable name followed by a period and the code completion window does not appear. Even using the menu option and keyboard shortcuts do not make the window appear.
No code completion window after typing the period for a web service object. Also tried the menu options and keyboard shortcuts for code completion and nothing happens.
Code completion window pops up like any other class/object.
How often does this happen?
All of the time.
Reference.cs is automatically generated by the Web Service wizard. Everything works as it should (as as it does in Visual Studio) - the object can be referenced and the project builds and runs successfully. It is just that the Code Completion Window does not appear for Web Service objects and so the methods and properties of the object are not known for their types and parameters as you are coding against it.
This is no longer a problem in XS 4.0.12. I am happy to close the bug.