Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

Cannot install WCF Connected Services without Microsoft Connected Services #4

Open
VeXHarbinger opened this issue Feb 21, 2017 · 10 comments

Comments

@VeXHarbinger
Copy link

Howdy All,

I just cannot figure this out. My IDE offers an Add Connected Service action with a few service options, just not the WCF one.
Every time I try to follow the steps to add the WCF Service option I receive the following error;

Install Error : Microsoft.VisualStudio.ExtensionManager.MissingReferencesException: This extension cannot be installed because the following references are missing:
-ConnectedServices.B3144AF8-5B8F-491C-9ACA-996350E8FE95 (Microsoft Connected Services)

I do have both of the requirements installed;

  • Visual Studio 2015 Update 3
  • .Net Core and ASP.NET Core 1.0 SDK

So I've gone around and around reinstalling these components, running a repair on my IDE but none seem to replace the missing Connected Service component it's looking for.
Any steps/ideas on how to resolve this or if there is a component that causes this error? I've need no results on Google and I'm at a loss as to what else I could do.

@VeXHarbinger
Copy link
Author

@VeXHarbinger
Copy link
Author

Anyone have any ideas? I'm still stuck with this issue

@GuyKh
Copy link

GuyKh commented Mar 22, 2017

I'm experiencing the same problem.
Both for WCF Connected Service and OData Connected Service

How can I add a reference to Microsoft Connected Services? 😞

@sjc01234
Copy link

I was also having this problem: got the extension installed (and restarted VS2015) but could not see WCF as an option to add a connected service. I had already started a .net core console app project before installing the extension and was attempting to add the connected service in this existing project.

So, I started two new projects:

  • .net core web app (blank/empty) -> I was able to see WCF as an option.

  • .net core console app -> I was able to see WCF as an option

So, not sure if this is actually a solution, but for me it appears that you need to start a new project after getting the extension installed.

@VeXHarbinger
Copy link
Author

Nope, i'm 100% blocked on this one. Had to take development to a new machine

@dmitry-pavlov
Copy link

The issue is still here - I have just got this while updating my VS2017 extension to support VS2019 preview.

I have reported this bug here - please vote for fixing it: VS2019 Preview: cannot install connected service extension updated from VS2017

@dmitry-pavlov
Copy link

According to Angelos Petropoulos [MSFT] · 17 hours ago

Microsoft Connected Services have been deprecated in VS 2019. Please use standard Visual Studio extensibility points instead: https://docs.microsoft.com/en-us/visualstudio/extensibility/

@AndrewBrianHall
Copy link

Saying that connected services is deprecated is not quite the right messaging. The team had been working on a set of new APIs that would provide richer functionality that the existing APIs and had take some proactive steps to try to help people not start new things on the old APIs. However, it was a mistake that existing extensions can't be installed and this will be fixed in the first update to Visual Studio 2019 (version 16.1)

@unchase
Copy link

unchase commented Apr 10, 2019

Thank you, we will wait for the update.

@CoolDadTx
Copy link

If there is a new set of APIs coming but we need to support connected services now what are the options? 16.1 will fix the issue that you cannot install a CS extension but what about even trying to build one? Trying to use the Microsoft.VisualStudio.ConnectedServices 16.0 NuGet package will still fail because the Microsoft.Developer.IdentityService.Client package isn't available in NuGet. We could go back to 15.3.47 which seems to be the last version of the Package that doesn't require it but how will that impact trying to build an extension for VS 2019?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants