Call API gateway endpoint using jQuery (Ajax)

-

The below shows one of the samples get calls to retrieve data from AWS API gateway -








Click!

Comments

Post a Comment

Popular posts from this blog

Windows Azure Package Build Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

-
Image
I often see when packaging Windows Azure project getting "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters." error. To fix this issue I had to change Cloud Project User options file add add ServiceOutputDirectory entry to the file. 1) Open your Cloud Project file in Windows Explorer from Visual Studio. 2) Find Cloud Project file in opened directory (*.ccproj file) 3) Open file in Notepad 4) Add c:\azure entry Now your cloud visual studio project user options file looks similar to below: 5) Save file and open your solution again. 6) Package Solution and it should package without above error.
Read more

Reset user settings on Visual Studio

-
Sometimes we might have created connection strings with different environments and don't want to save in entity framework wizard. Today I realized we can't modify/delete individual connection string from wizard. In order to delete saved connection strings from wizard we need to reset the user data. You can run the following command to reset user data on Visual studio: 1) Open Command Prompt 2) Goto C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE 3) Run devenv/resetuserdata It clears your profile  Visual studio settings and you can start creating new connection strings, which will be saved into your profile again.
Read more

WCF REST 400 Bad Request

-
Today while I was writing my WCF Rest Client, I was getting error as "400 Bad Request". Finally I realized the culprit of error was service name in web.config file. In order to resolve this error, make sure service name is matching with your service markup's service name. If you have servicename1.svc, right click on that file and select "View MarkUp". Copy Service value from that and paste it into webconfig's services service name. Service1.svc MarkUp: <% @ ServiceHost Language ="C#" Debug ="true" Service ="MyServiceNameSpace.Service1" CodeBehind ="Service1.svc.cs" %> Web.config Services Section: < services >    < service name = " MyServiceNameSpace.Service1 " >      < endpoint address = "" behaviorConfiguration = " restService "            contract = " MyServiceNameSpace.IService1 " binding = ...
Read more