Empty reference.cs file

So go ahead and add the Console. WriteLine call below. When Visual Studio loads a project with an analyzer, it is using the generator assembly which is available at the time that it loads. And that is the code which powers what is available to you during design time for IntelliSense. You can learn more and check on progress towards fixing this issue here.

When a change to a generator does not alter the API of the code it generates, we can work around this to a degree. There is a little bit of a workaround you can do here. This will ensure ConsoleApp always uses the right version of the generator when it is built. If you DO need to see the changes in the generated code, you still need to restart. So, I find this makes iterative development a little less tedious, but not that much. If we need to change the API of our generated code or if we want to alter the compiler warnings or errors output by our generator, then we should build the generator and then do a full restart.

When we build, we will get a build failure. This is only happening because of the pre-build clean step added above. What we can do is add a compiler directive which will launch a debugger that is attached to our generator. With this in place, we can add breakpoints wherever we need. Finally, we want to get our generator packaged so it can be used in other projects. If you want, you can check off Generate NuGet on build, so it generates every build. Importantly, for every version you want to actually publish and use, you need to update the version numbers.

You may be aware, you can change the file extension of a. I also have a copy of the nuget. Now that this is published, we can add another ConsoleApp to this solution or a different one, called ConsoleAppNugetConsumer. Now we can add this NuGet package to our app. The default namespace is the global namespace. The default filename is derived from the service name. The default is to use the system proxy setting. The default is to not read from the config file.

The appsettingurlkey option must also be specified. The url fragment is the result of calculating the relative url from the appsettingbaseurl to the url in the WSDL document.

Generate an abstract class for an xml web service implementation using ASP. NET based on the contracts. The default is to generate client proxy classes. Net Web Service. An interface is generated for each binding in the wsdl document s.

The wsdl alone implements the wsdl contract classes that implement the interface should not include either of the following on the class methods: Web Service attributes or Serialization attributes that change the wsdl contract. This allows you to specify options not available from command line such as choosing which type of asynchronous programming model is generated. For details, please see the tool documentation.

How are we doing? Please help us improve Stack Overflow. Take our short survey. Has anyone encountered this? Improve this question.

Barth 8, 71 71 gold badges 48 48 silver badges 63 63 bronze badges. Matt Matt Add a comment. Active Oldest Votes. Improve this answer. Anderson Imes Anderson Imes ObservableCollection to Generic. List — Yossi Dahan. Happened to me because I added on to the partial class.

However if you wanted to use types from a specific assembly, you can select just that assembly and it works just as well at least in my case , ta — Dead. It boggles my mind that I get an average of 50 points per week from this question even 6 years later. Come on MS, fix this. At least give the developers some feedback when this goes poorly instead of having them stare at a blank file.

Thank you! Show 2 more comments. As an enhancement here is a quick example of using svcutil. In my case, this came about after I referenced an assembly that also referenced my WCF service. Removing that assembly from the list of assemblies to share types with fixed it. I was getting a meaningless error message just a namespace when adding a Service Reference and this pointed out the issue.

John Saunders John Saunders k 25 25 gold badges silver badges bronze badges. How to run svcutil. Arul: Use Google to find information on svcutil. Not sure if Microsoft has read this post but even just showing a message box saying the errors and warnings instead of just silently putting them in the minimized, in my case Error List window would have made it so I didn't need to Google this.

All rights reserved. Warning: No code was generated. Verify that you passed all the metadata documents to the tool. Matt Kane Matt Kane 1 1 silver badge 6 6 bronze badges. Remove the service reference having issues. Click on the project name in the Solution Explorer to highlight the project. Right-click on the project reference. Near the top of the context list, click the Clean item.

Add your service reference as you normally would. Hope this helps. This one did it for me, other solutions resulted in an empty Reference. I had this problem with a Silverlight 5 upgraded from a previous version.

Even re-adding the service reference still gave me an empty Reference. Jon Person Jon Person 1 1 silver badge 3 3 bronze badges. My issue was that I left the " mex " onto the end of my web service link. This is so obvious but so easy to overlook or dismiss as unimportant.

Then you just have to guess what's wrong with that code. Some error feedback in the tool would have helped, of course. JoshuaLawrence JoshuaLawrence 5 5 bronze badges. Commenting out all of the operation contracts worked for me. I was looking at the wrong methods as the culprit.

Thanks for the back to basics approach to troubleshooting. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Collectives on Stack Overflow. Learn more. WCF Error - Reference. Asked 10 years, 8 months ago. Active 5 years, 8 months ago. Viewed 5k times. Improve this question.