3 ms·
You might want to look into Backbone.js (or Ember.js or Angular.js) rather than Bootstrap for talking to APIs. Also, you haven't said if the existing code is W
by macca321 14y ago
You might want to look into Backbone.js (or Ember.js or Angular.js) rather than Bootstrap for talking to APIs.
Also, you haven't said if the existing code is WebForms or MVC (and the fact that you haven't makes it seem like you may struggle to finish the server side code using ASP.NET).
Which platform were you thinking you would develop the REST API on if not ASP.NET?
- alliemobley 14y agoAsp.net webforms, I ought to have clarified that. The REST API i'll create with javascript, perhaps using this c# to javascript compiler: http://www.erik-kallen.se/blog/saltarelle-open-source-c-to-javascript-compiler http://www.erik-kallen.se/blog/saltarelle-open-source-c-to-j... to reuse some of the c# once I decouple the objects from the user interface/data. The problem with the code right now is application logic is mixed with the data and display logic. I feel like I can add more value by removing dependencies for asp.net/mssql and trading them for free/open source software. My concerns are: Build it to scale as cheaply as possible. Make it so I can add functionality to the web/native apps by adding new services to the api, to stay dry. Stay flexible for future iterations/pivots. At some point windows/ios versions will come up, so I'm just trying to excersize some economy of motion here. If I create wcf services, we will have to purchase visual studio licenses when we start hiring developers to maintain them.