Unable to add service reference in VS 2017 15.5.7 - c#

I have a VB.NET Core app I'm trying to connect to a remote WCF service. When I try going through the "Add Connected Service" routine, no services are listed and a message shows up saying that:
no connected service is supported for the current project type.
I tried installing the WCF Web Service Reference Provider extension - which IIUC shouldn't be required anymore since 15.5 - but it made no difference.
What am I doing wrong here?

First, Uninstall the "WCF Web Service Reference Provider" by going into through Tools -> Extensions and Updates menu in VS. This has been in VS since the release of VS 15.5.5. So if you have 15.5.7 then having the extension installed could be causing issues.
I created a .Net core application and when I click on the "Connected Services" link I get the following screen.
Then when I click the "Microsoft WCF Web Services Reference Provider" link I get the following screen.
I am running VS 15.5.7, so you should see the same screens. What do you get when you do the same steps? Can you post some screen shots?
Sorry I could not go past this screen, I did not have a WCF web service I could access to see what the next steps are. If you have issues following the steps above, please post more details about what you are seeing (screenshots would help). Also, if you have a URL to a public WCF service please post it so I can see if I have the same issue you are having.

So it looks like when the .NET Core project is in VB.NET the WCF Web Service Reference Provider isn't available. Quite disappointing if you ask me. :(

Related

Service Fabric services debugging issues

I have 2 Service Fabric services, which I need to debug. Those services communicate with each other.
I am using:
VS 2017(update 7),
.NET Framework 4.6.1,
Azure SDK 2.9.5.3,
Service Fabric Tools 2.0.20180124.2,
Service Fabric 6.1.456.9494,
Service Fabric SDK 3.0.456.9494
Everything was going alright, but at some point I've started to get following errors, when I try to start debugging 2nd service.
I don't understand why I am getting those errors.(Google produces absolutely nothing on those errors) Here they are:
1st error: Error MSB4064 The "ProjectReferencesWithConfiguration"
parameter is not supported by the "GetServiceProjectReferences" task.
Verify the parameter exists on the task, and it is a settable public
instance
property. \packages\Microsoft.VisualStudio.Azure.Fabric.MSBuild.1.6.5\build\Microsoft.VisualStudio.Azure.Fabric.Application.targets 95
2nd error:Error MSB4063 The "GetServiceProjectReferences" task could
not be initialized with its input parameters.
\packages\Microsoft.VisualStudio.Azure.Fabric.MSBuild.1.6.5\build\Microsoft.VisualStudio.Azure.Fabric.Application.targets 94
Here is complete scenario:
One of the services(does not matter which one) in one copy of VS has started successfully without errors.
I've trying to start 2nd service in another copy of VS. And during this attempt I'm getting errors I've mentioned above.
To remedy the situation I have to close offending copy of the VS and open ServiceFabric service project in new VS copy and after that service will start successfully.
Unfortunately all that dancing are getting quite annoying because it's taking up A LOT OF time.
Any help would be appreciated.
I solved this by upgrading Nuget package Microsoft.VisualStudio.Azure.Fabric.MSBuild from version 1.6.4 to 1.6.5
After that also had to manually change 1.6.4 to 1.6.5 in the .sfproj file, as Nuget package manager did not do that automatically.
I had the same issue after upgrading Visual Studio to version 15.6.4 (can't remember what my previous version was). Tried altumano's solution of updating Microsoft.VisualStudio.Azure.Fabric.MSBuild and ran into other errors.
Solution that appears to have worked for me is to upgrade Visual Studio again to version 15.6.6. I still plan to update Service Fabric SDK to a more recent version, but so far this Visual Studio update alone has solved my issue.
It looks like updating Service Fabric SDK to 467 version did the the trick.
I've been working all day today and didn't see pesky error messages during services start up. Now I have in Control Panel\Programs and Features following lines:
Microsoft Azure Service Fabric 6.1.467.9494
Microsoft Azure Service Fabric SDK 6.1.467.9494
Upgrading Visual Studio to version 15.6.7 and Service Fabric SDK to version 3.1.269 seems to work.

UWP VS2015 .Net 4.61 Add Web Reference Button Missing

Any help would be greatly appreciated!! I have scoured the web trying to find an answer. I am writing a UWP app that will be deployed to the Xbox platform. I need to access a web service written in .Net 2.0. In earlier versions of .Net / Visual Studio the Add Web Reference Button was hidden in a panel accessed through ->Add Service Reference ->Advanced ->Add Web Reference. With latest build of VS2015 the Add Web Reference Button is missing. Did this completely go away or is it hidden even deeper in the environment somewhere?
XML Web Services, also known as ASMX services, were the predecessor of Windows Communication Foundation (WCF). You can access Web Services by adding a service reference just as you would for any other WCF service.
A service reference enables a project to access one or more Windows Communication Foundation (WCF) services. Use the Add Service Reference dialog box to search for WCF services in the current solution, locally, on a local area network, or on the Internet.
For more info, please How to: Add, Update, or Remove a Service Reference.

Azure Service Fabric continuous integration fails in Visual Studio Team Services (was VSO)

I have tried to set up continuous integration to deploy my Azure Service Fabric cluster automatically on git push events in Team Services. I followed the default template for a Team Services Build Definition and a Team Services Release Definition based on this guide:
Set up continuous integration for a Service Fabric application by using Visual Studio Team Services
Here are my settings:
For the most part everything works for the first deployment. After that it throws the following error:
An application with name 'fabric:/<APP>' already exists, its type is '<APP>Type' and version is '1.0.0.20160812.7'. You must first remove the existing application before a new application can be deployed or provide a new name for the application.
From that it appears as though it is trying to completely redeploy the service instead of just upgrading the service. I have searched through all of the settings and tried creating and recreating the tasks but have not been able to resolve.
Has anyone encountered this before?
You need to add or update a publish profile to enable the upgrade mode and use that profile to deploy the Service Fabric after the first deployment is succeed.
To do this quickly, you can right click on your project and select "Publish" from Visual Studio, check "Upgrade the Application" option and click "Configure Upgrade Settings" if needed, and then click “Save Profile" link and commit/push the changes.
Though there is an accepted answer, I would still like to add to this thread. In the approach below we need to edit only the Azure Devops Task. Hopefully this will be useful to others who may encounter the same issue: One simple workaround when you encounter this issue is to change the "Overwrite Behavior" under the Advanced Setting for the build task to "Always". However, care must also be exercised so that if there are services which may already be running - all of them do get upgraded via a rolling upgrade (see second image).
To ensure that rolling upgrade is applied to all the services, in addition to the above, also ensure that the upgrade settings are configured as below:

Error when adding a Service Reference for a Web Service

I am in a .NET programming class and am creating a simple web service and a console tester to work with it. I am using C#, the IBM .Net data provider (have also tried it with the OLE DB data provider) - both data providers can successfully access and retrieve/update data from the server, and the .NET Framework 3.5.
The web service works, the console tester works (in it's current state), but when I try to add the service reference to link the two together I am getting the following error:
Method not found: '?'.
Metadata contains a reference that cannot be resolved: 'httppp://localhost:64302/WebServiceV2/Service.asmx'.
Metadata contains a reference that cannot be resolved: 'httppp://localhost:64302/WebServiceV2/Service.asmx'.
If the service is defined in the current solution, try building the solution and adding the service reference again.
VS 2010 is able to discover the reference, but when I try to expand the webservice.asmx file or if I press OK, I get this error.
I am running VS 2010 Pro SP1 on a Windows 7 machine (64 bit), on a PC that I use for work.
I have tried to "repair" VS 2010 and I have uninstalled/re-installed it but cannot get around this error. As mentioned I have installed SP1. Also I have installed the "CU3" update, which from what I can tell is a "cumulative" update for VS 2010.
I have discussed this error with my class instructor, fellow co-workers, and the CTO of my company. None of these people have experienced this nor can they duplicate this error with VS 2010 and are at a loss to explain it. This leads me to believe that VS 2010 is okay but there might be something else on my PC that is causing this error - or perhaps I might be missing a key update of some sort. My next approach will be to install this on my home PC (Windows 7 as well) to see if I get different results.

WCF Data Services is not installed for this target framework. (Set up of WCF Console Application Client)

I am currently trying to set up a WCF Data Service Client using Visual Studio 2013 Desktop. The following guide shows how to set it up as a console application, but every-single-time I try to add a Service Reference VS says:
Unable to add a service reference to the specified OData feed because
WCF Data Services is not installed for this target framework. To install
a supported version of WCF Data Services, see
http://go.microsoft.com/fwlink/?LinkId=253653.
Is there something I am missing or is it even possible? I've added and tried multiple different different References for the WCF data to no avail. Suggestions?
Though op question has been resolved, I am adding this answer so that it can help any other with the same problem.
The solution is to to download and install WCF Data Service RTM Tools as suggested in link provided by Microsoft in error itself.
More more details refer:
http://www.microsoft.com/en-us/download/details.aspx?id=39373
http://msdn.microsoft.com/en-us/jj658961

Categories

Resources