Tag Info

New answers tagged

2

At my job we do this currently fairly easily just by putting each version under it's own application folder in IIS, so we have URIs like: http://SomeServiceBox/Service/v1.0/ http://SomeServiceBox/Service/v1.1/ http://SomeServiceBox/Service/v2.0/ http://SomeServiceBox/Service/v2.3/ Works just fine for us. I can only suggest this until you explain why you ...


1

You want to use the DependencyResolver Class. http://msdn.microsoft.com/en-us/library/system.web.mvc.dependencyresolver(v=vs.118).aspx In your global asax, you set the resolver and wire up fake implementations of interfaces that your data access layer also implments Then in your controller, you create 2 constructors public Controller() : ...


0

If you want a request sent after a confirmation dialog is shown it's up to you, via client code, to do that. The browser will not take any initiatives for you there. On its own it only can tell it must send a request when a form is submitted, a link is clicked or a new address or search query is submitted. That's it. Other than that, it never knows. So the ...


1

You can certainly use any mix of client-side rendering and server-side rendering, but I would recommend against trying to mix ASP.NET MVC helpers with AngularJS directives. It might seem like a good idea at first because you're already used to using those helpers and you don't have to write "raw html", but they defeat the some of the purpose of what ...


1

I am building an app that is a combination of MVC on the server and AngularJS on the client. On the server: I found the easiest thing to do was to build a bunch of RESTful web api's to provide data services to the client. I also perform validation on the server to make sure that no one cheats (sending data using a client other than the web page). I also ...


2

A bit of an outsider comment/answer, I'm not a .NET MVC programmer but have done a lot of PHP, Java, and AS3 programming and relatively recently switched to AngularJS as well. My general feeling is that the back end should just be RESTful and shouldn't touch the front-end really and the front-end should only depend on the back end for data. There are some ...


2

As with many options, both would work. Between those two I think the base controller is the more correct option. The "models" you tend to see in MVC projects these days are leaner with just properties and few to no methods. If you want a more correct alternative, consider putting this logic in a separate "repository" class. This way you can keep the ...



Top 50 recent answers are included