- Whats Web is the easiest and fastest application that you can open chat messenger application on your mobile and Control another account with the same device!!! Whats Cleaner: The most important.
- Quickly send and receive WhatsApp messages right from your computer.
Web API Client Support for Windows Phone 8.1. You can now use the Web API Client NuGet package to implement your Web API client logic when targeting Windows Phone 8.1 or from within a Universal App. Known Issues and Breaking Changes. This section describes known issues and breaking changes in the ASP.NET Web API 2.2. OData v4 Model builder.
by Microsoft
This topic describes what's new for ASP.NET Web API 2.2.
Download
The runtime features are released as NuGet packages on the NuGet gallery. All the runtime packages follow the Semantic Versioning specification. The latest ASP.NET Web API 2.2 package has the following version: '5.2.0'. You can install or update these packages through NuGet. The release also includes corresponding localized packages on NuGet.
You can install or update to the released NuGet packages by using the NuGet Package Manager Console:
Documentation
Tutorials and other information about ASP.NET Web API 2.2 are available from the ASP.NET web site (https://www.asp.net/web-api).
New Features in ASP.NET Web API 2.2
OData v4
This release adds support for the OData v4 protocol. For more information, see the Web API OData v4 documentation.
Here are some of the key features and changes for OData v4:
- Integrate with ODL UriParser
- Support for enum, containment and singleton
- Support cast for primitive types
- Support for cast() in $filter
- Support for open complex type
- Removed EntitySetController and AsyncEntitySetController
- Uses OData Core Libraries 6.4.0
Attribute Routing Improvements
Attribute Routing now provides an extensibility point called IDirectRouteProvider, which allows full control over how attribute routes are discovered and configured. An IDirectRouteProvider is responsible for providing a list of actions and controllers along with associated route information to specify exactly what routing configuration is desired for those actions. An IDirectRouteProvider implementation may be specified when calling MapAttributes/MapHttpAttributeRoutes.
Customizing IDirectRouteProvider will be easiest by extending our default implementation, DefaultDirectRouteProvider. This class provides separate overridable virtual methods to change the logic for discovering attributes, creating route entries, and discovering route prefix and area prefix.
Following are some examples on what you could do with this new extensibility point:
Support inheritance of Route attributes
Example:
Here a request like '/api/values/10' would successfully return 'Success:10'
Provide a default route name for your attribute routes by following some convention you like. By default, attribute routing doesn't automatically create names for attribute routes.
Modify attribute routes' route template at one central place before they end up in the route table.
Web API Client Support for Windows Phone 8.1
You can now use the Web API Client NuGet package to implement your Web API client logic when targeting Windows Phone 8.1 or from within a Universal App.
Known Issues and Breaking Changes
This section describes known issues and breaking changes in the ASP.NET Web API 2.2.
OData v4
Model builder
Issue: Overloaded Functions could not be exposed as FunctionImport
If there are 2 overloaded functions and they are also FunctionImport as shown below then requesting ~/GetAllConventionCustomers(CustomerName={customerName}) results in System.InvalidOperationException.
Workaround: The workaround for this issue is to add both the function overloads as FunctionImports.
OData Routing
String literals that include the URL encoded slash (%2F), and backslash(%5C) cause a 404 error when they are used in the OData resource paths.
For example, string literals can be used in the OData resource paths as parameters of functions or key values of entity sets.
/Employees/Total.GetCount(Name='Name%2F')
/Employees('Name%5C')
When services receive such requests the hosts will un-escape those escape sequences before passing them to the Web API runtime. This protects against attacks like the following:
http://www.contoso.com/..%2F..%2F/Windows/System32/cmd.exe?/c+dir+c:
This causes the Web API OData stack to return a 404 error (Not Found). To prevent this error, your client should use the double escape sequences for slash (%252F) and backslash (%255C). This does not happen for query strings such as /Employees?$filter=Name eq 'Name%2F'
Note un-escaped slashes ('/') and backslashes (') are not legal in OData resource path string literals. Slashes should appear only as path separators and backslashes should not appear in the OData resource path at all. (Both are usable in some portions of an OData query string.)
Workaround: You could override the Parse method of DefaultODataPathHandler to escape the slash and backslash in string literals before actually parsing them. You can find a sample of this approach here.
OData v3
[Queryable]
The [Queryable] attribute is deprecated. New OData v3 applications should use System.Web.Http.OData.EnableQueryAttribute.
The ODataHttpConfigurationExtensions.EnableQuerySupport extension method now adds an EnableQueryAttribute to the global filter collection. If any controllers have the [Queryable] attribute, calling config.EnableQuerySupport() will cause the [Queryable] attribute to fail
The recommended way to resolve this issue is to replace all instances of QueryableAttribute with System.Web.Http.OData.EnableQueryAttribute.
An alternative workaround is to use the following code in your Web API configuration:
Attribute Routing
Issue: Model binding of complex type which is decorated with FromUri attribute behaves differently when using Attribute Routing.
Following link is tracking the issue and also has details about a workaround.
http://aspnetwebstack.codeplex.com/workitem/1944
Issue: Scaffolding MVC/Web API into a project with 5.2.0 packages results in 5.1.2 packages for ones that don't already exist in the project
Updating NuGet packages for ASP.NET MVC 5.2 does not update the Visual Studio tools such as ASP.NET scaffolding or the ASP.NET Web Application project template. They use the previous version of the ASP.NET runtime packages (e.g. 5.1.2 in Update 2). As a result, the ASP.NET scaffolding will install the previous version (e.g. 5.1.2 in Update 2) of the required packages, if they are not already available in your projects. However, the ASP.NET scaffolding in Visual Studio 2013 RTM or Update 1 does not overwrite the latest packages in your projects. If you use ASP.NET scaffolding after updating the packages of your projects to Web API 2.2 or ASP.NET MVC 5.2, make sure the versions of Web API and ASP.NET MVC are consistent.
Bug Fixes and Minor Feature Updates
This release also includes several bug fixes and minor feature updates. You can find the complete list here:
Microsoft.AspNet.OData 5.2.1
The Microsoft.AspNet.OData 5.2.1 package contains NuGet dependency updates but no bug fixes. With this update, there is no longer a strict dependency on Microsoft.OData.Core 6.4.0, but one can upgrade to any version between 6.4.0 and 7.0.0.
Microsoft.AspNet.WebAPI 5.2.2
In this release we have made a dependency change for Json.Net 6.0.4. For more information on what is new in this release of Json.NET, see Json.NET 6.0 Release 4 - JSON Merge, Dependency Injection. This release doesn't have any other new features or bug fixes in Web API. We have subsequently updated all other dependent packages we own to depend on this new version of Web API.
Microsoft.AspNet.WebAPI 5.2.3 Beta
You can read about the release here. This release contains only bug fixes. You can use this query to see the list of issues fixed in this release.
WhatsApp web is the most prominent and most convenient messaging application people use. Around 1.5 billion active users are present to use WhatsApp. Making voice calls and video calls through WhatsApp is more accessible, but at the same time, it is a tedious job to do on a desktop. People find making video calls through WhatsAppWeb very much challenging. Now, the best is we came with a solution to this query. In this guide, we have a smart solution for the users. The demonstrated details would elaborate on the WhatsApp Video Call feature and how to make the Video Call through WhatsApp Web easily as a professional. So, let me now start with listing the solution without wasting a single minute.
Whatsapp Web Video Call – It is Possible?
If anyone out there is seeking the WhatsApp Web Video Call feature, you may face disappointment, but there is no such feature yet. No doubt, one can access use WhatsApp over the desktop or Mac with WhatsAppWeb, but still, the provision of making a video call is not yet launched. For now, users can only make video calls via their Android iOS.
The WhatsApp web has the only feature of chatting options and attachments also; but if we talk about making video calls, it is still missing somewhere. The feature is not available over windows and Mac too. As of now, the user needs to wait until the function has launched.
Whatsapp Download For Pc
Make a video call over desktop through WhatsApp?
Yes, we know you got disappointed after reading the above paragraphs, but not it is the time to charge you up. Still, we have a solution for you, from which you can make a video call through WhatsAppWeb.
Making the WhatsAppWeb video call over a desktop is not possible, but you need to use an emulator. The user does not need to pay for the emulator. You can easily find the free Android emulators through which one can make WhatsApp video call over desktop.
The free android emulators are also worthy of use. The emulator will help to access the original version of WhatsApp as you use on your phone. Your desktop will run the original form of WhatsApp with the help of an emulator, which has a feature of voice calls and video calls.
Follow up the steps to use the original form of WhatsApp over the desktop:
What's Web App
- First, download the emulator over desktop or Mac, and then install it. Just read and agree on the terms and conditions that come in the installation process.
- Now you need to wait for some time, and then the emulator will install the application. Once you have installed the app, you will notice the same.
- It might take time later on but then enter your Google account credentials. Put the account details, which are linked with the device.
- Once you have installed the application, then you need to search for WhatsApp over the search bar.
- Install the application and enter the registered number. The original WhatsApp will work on the desktop. After that, your contacts will be retrieved automatically. Just choose any contact and make a video call by clicking on the video call button positioned at the above of the screen.
Final Words:
I hope that now you will make WhatsApp video calls very quickly from your desktop by following the demonstrated steps above. Accessing the WhatsApp video call feature is not as easy as the chatting and attachment feature. If you need WhatsApp for texts and attachments, normal WhatsAppWeb is fine to use. But in case of a video call feature, make sure to use a quite better emulator for the same as well.
