Trying to update Service Reference in an existing project, I got an error that says,
The specified OData API cannot be updated because OData APIs are now only supported with Connected Services.
The aka link (http://aka.ms/odatavsclientguidance) leads to http://odata.github.io/odata.net/#OData-Client-Code-Generation-Tool.
There is no instruction for VS 2017.
The instruction below leads me to the OData Connected Serve VS extension.
(https://marketplace.visualstudio.com/items?itemName=laylaliu.ODataConnectedService)
And it appears that extension cannot be installed in VS 2017.
Scroll to the bottom of the extension description page, we will see all the questions about its VS 2017 version.
So the question: is that OData extension the only to update OData Service in VS 2017? What walk around do we have?
The official Visual Studio Marketplace code generation tool, which you refer to in your post, now supports Visual Studio 2017.
One notable difference from how one would normally go about setting up OData references is that where one would previously use Visual Studio's "Add Service Reference" directly to generate the relevant code, installing the tool adds a "Add Connected Service" instead.
See also the discussion in this GitHub issue.
In your Solution Explorer, right click on References, Add Connected Service then select Microsoft WCF Web Service Reference Provider, you'll get a Wizard-like window to add a Service Reference just like in VS2015.
Refer to https://learn.microsoft.com/en-us/dotnet/core/additional-tools/wcf-web-service-reference-guide
Images at https://imgur.com/a/6kYhexK
Related
My colleagues and I have several versions of Visual Studio installed which — for business reasons — we may need to keep for some time. For some teammates an inconvenient version of Visual Studio will open when cloning a git repository from Azure DevOps server, starting from this web UI:
How can we ensure the preferred version of VS opens upon/after cloning? As a bonus, would there be any way to configure this per repository?
So far the best we have worked out is to follow these steps. However it doesn't seem to consistently update the preference for every user. In particular, if a team member has already cloned at least once targeting an earlier version (e.g. VS 2015, VS 2017) we seem to have a dickens of a time getting an update of this preference to VS 2019 to stick.
Open “Default Apps” in system settings
Select “Choose default apps by protocol”
Scroll to “Microsoft Visual Studio Web Protocol Handler Selector"
Change handler to Visual Studio 2019
Note: Our machines have MS VS Web Protocol Handler Selector listed twice. We have experimented with setting both or either without success. Any suggestions why we're seeing the protocol selector twice may also help.
would there be any way to configure this per repository?
For this issue, I am afraid this is currently not achievable in azure devops.
As a workaround ,agree with James Z, you can perform cloning in a specific version of visual studio instead of from the web UI from azure devops, so you don't have to worry about the troubles caused by the default version. In addition , the MS VS Web Protocol Handler Selector icon for vs2017 and vs2019 looks almost the same, which is also easy to confuse.
Open a specific version of visual studio according to your needs, connect to your project in Team Explorer, and select the repo to be cloned.
I installed elmah and I have got it fully working, however they also provide a visual studio extension - However when I try use it visual studio gives me an error saying:
"The Visual Studio Extension requires API V2 to be enabled"
Any ideas what that actually means, and what I need to do to "enable API V2" for visual studio?
API v2 can be enabled through the log settings view. The easiest approach is to navigate to the settings screen of the log you want to browse from the Visual Studio extension as described here: https://docs.elmah.io/where-is-my-log-id/. When on the log settings screen, click the Actions tab. On this tab, you can enable API v2.
We are planning a major overhaul of the VS extension which will allow for the extension to communicate with API v3 (the default containing improved security).
It looks like Visual Studio 2017 switched its online reference documentation from .Net Framework to .Net Core: every time I hit the F1 key, I get sent on .Net Core documentation for the type/method on which the caret was.
Very well if I were in a .Net .Core project, but it does it too on .Net Framework 4.6.1 projects. And on this .Net Core help, there is no Show other versions drop down list. (Which is understandable, that is not really a newer version of .Net Framework 4.x.)
This renders this key almost useless to me. I end up googling the type / method for getting the MSDN .Net Framework 4.x documentation. (Which is currently more complete for subjects existing in both, compare this and this.)
Is there any way to get the F1 key to open from Visual Studio 2017 the .Net Framework 4.x documentation for the type/method on which the caret is?
I have found no settings for that neither in Help nor in Tools/Options.
This issue affects only online help. Technically Visual Studio does not seem to be blamed. It launches the browser on a MSDN website url with parameters specifying the framework and its version. But MSDN redirects regardless to .Net Core documentation. So it now appears to me as a MSDN website bug.
Example url on which Visual Studio 2017 sends:
http://msdn.microsoft.com/query/dev15.query?appId=Dev15IDEF1&l=EN-US&k=k(System.Runtime.Serialization.StreamingContext);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.6.1);k(DevLang-csharp)&rd=true
Resulting MSDN redirection: 301 => https://msdn... then 302 =>
https://learn.microsoft.com/en-us/dotnet/core/api/system.runtime.serialization.streamingcontext
While Visual Studio 2015 sends on:
http://msdn.microsoft.com/query/dev14.query?appId=Dev14IDEF1&l=EN-US&k=k(System.Runtime.Serialization.SerializationInfo);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.6.1);k(DevLang-csharp)&rd=true
Which only redirects to the https version of the url, then serves the page.
Now this has changed.
As already stated in my question edit, that is more a documentation web site trouble than a Visual Studio trouble.
Moreover, the learn.microsoft.com web site has now changed its redirection. For the provided example, it now gets redirected to (no more core in the path):
https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.streamingcontext
Which redirects further to:
https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.streamingcontext?view=netframework-4.7
Well, still not the asked framework (4.7 instead of 4.6.1), but way better than landing on .Net Core documentation instead of .Net Framework.
It also looks as complete as msdn documentation, though not giving the option to see documentation for versions prior to 4.5.
And indeed in my few tests, changing the version does not seem to reload the page, it seems a bit cosmetic for now... In fact, that is the Core reference documentation which is now gone!
So that move from msdn to docs looks like a bit premature, the learn.microsoft.com site seems to be still a "work in progress" site.
Anyway, it does not look to me there is anything to do on Visual Studio 2017 side. Just wait for the new documentation site to get finished.
Whenever I update WCF service reference in front end project, the service reference update happens and the bottom left corner of Visual Studio indicates that the service reference update is complete, but Visual Studio becomes non responsive after the update. If I close the Visual studio using the Task manager and restart it, reopen the solution, I can proceed as normal and can use the updated service reference. For now I always restart my Visual studio and reopen my solution to continue working on my tasks. Has anyone faced this issue? If anyone found the solution for this issue, could you please help me fixing this as it is very annoying to restart the Visual studio every time I update the service references. Thank you.
(I am using Visual Studio 2013 - project uses .Net Framework, asp.net webforms, and C# as the language for development. - if it helps.)
After trying different options, I guess the size of sln file and the size of references caused the issue for me. We use Resharper in our company which adds extra load when updating the service references.
My Visual Studio doesn't hang/becomes not responsive (most of the times), when i do the following..
1) Go to Tools -> Options -> Source Control - change the default option from Microsoft Git Provider to None.
2) Tools -> Options -> Resharper Ultimate and disabl it.
3) Try to figure out which projects in the solution is not required or affected and unload them.
Then update the reference. Still sometimes it doesn't work for me, but most of the times i dont have to restart the solution using task manager. I always disable resharper before I have to update the service reference and enable it back again once the service reference is updated. Hope it help others if they face similar situations..
Is there any Visual Studio 2010 add-in available for Rocket U2 .NET Database Provider (Universe)? I know there is a tool for 2008 but I can't get this new U2 .NET tool Kit working and generate an ERM.
The answer to your first question is: yes there is.
Both the .NET Toolkit and UniObjects for .NET should work seamlessly with VS 2010.
You can download the necessary software from the Rocket U2 website under "resources/downloads"
You can also use UniObjects for .NET which is available in the "u2-Clients" download on the Rocket website. This is a DLL which you then add as a reference in your Visual Studio project and makes it possible to interact with your UniVerse database and data. The documentation on how to use both products is also available there for download.
If this does not help, ask a more specific question stating the exact error messages you are getting, together with details of which .NET framework version you are using and UniVerse platform and version.
I would like to inform you that U2NETDK V 1.2.0 will have new product called U2 Database Add-ins for Visual Studio. It will allow you Server Explorer Integration that simplifies U2 data access in .NET. You will see U2 Tables, Views and Subroutines in Server Explorer and you can drag and drop in Designer such as DataSet Designer / Entity Data Model Designer. We will go EAP soon.
One more thing, I want to add that you do not need any more 'UniObjects for .NET' as this functionality is added into 'U2 Toolkit for .NET' Product. We have sample code in the installation that demonstrates 'UniObjects for .NET' functionality.