Why would you ever use asp.net’s ViewState storage object over the Session storage object?
Other than because session storage is session-global to more than one page, why would you ever want to use the viewstate to hold values?
Other than because session storage is session-global to more than one page, why would you ever want to use the viewstate to hold values?
What is the best method of securing a REST Web API with the following requirements. The system has an Angular JS frontend with the REST APIs implemented in ASP.net.
I want to create the web application which will be based on angularjs frontend and ASP.NET Web API. I need create the secure api but I can’t use the token based authentication on the company’s server where will be implemented this web application.
I have an application that have four modules in the front end, I’m trying to use as much as possible AngularJs in the front end I’m using an empty website asp.net project to host all the files and the REST serviceStack, my project have kind of the following structure:
I have an Angular application that I’m trying to authenticate with Basic authentication to my REST service. I’m adding the authorization header with the corresponding “Base {username:password}” encoded in base64 and I’m calling my rest api but keep getting back a 401. I’m obviously missing a step here…
This is an intranet app.
I am starting my own Angular web application. I have experience coding in c# and angular but I have never had to set up my own project/solution. In this case, I would like to set up an ASP.NET Web API that will communicate to an Angular SPA front end in JSON (although it should be agnostic to the front end, any application that speaks JSON should be able to communicate with it).
I have an ASP.NET Web API running locally on some port and I have an angularjs app running on 8080. I want to access the api from the client.
I am using Visual Studio 2013 Update 4 and I have a web api project setup to receive get requests that returns an array. For the client app I have setup cordova and am emulating an android angular app using ng-resource to call the web api get. Everytime I call the GET I get a ripple.js error that says connection refused. I get the connection refused even if I try with a real android device as well. Here is the error when using the ripple emulator
I’ve created Angular application based on routes.
Without using the routes, the Signalr works fine, but when I work with routes, the Signalr works just in one way – from client side to server.