Tag Info

Hot answers tagged

4

I don't see a need for two controllers. You're dealing with one type of resource (Person), but asking for data in two formats (summary and detail). I would leave it at one controller and go on with life.


1

The biggest change is that the web front end (the part that runs in the browser) has gotten more sophisticated. There are many frameworks that provide enriched functionality at the client; Angular is just one of them. You can look here to find out more about what frameworks are available and what functionality they provide. There is the notion of a Single ...


1

Yes and no. Yes because it would not be hard to fix the pain points in step 2 or 3 without much trouble -- just redo your packaging to call msbuild on individual projects with a desired output directory so you don't have to maintain the file lists at least. Yes because you could probably dodge the whole github package by perhaps deploying your built ...


1

This can be done using a WCF CallBack contract. If the client can make a connection to the server, the server can use a WCF service with a callback construction. This describes that the server expects the client to implement a service as well (the callback service), as part of the service contract. This beaks down as follows: The server hosts a WCF ...


1

Since the user has to enter his data into a form, simply save that to the database. A common way to do this could be to have a user table with a user ID, and a flag or status code stating that the record is inactive and needs administrator attention. From here, the web app should send a link to the administrator with the user ID embedded in the URL. It ...



Only top voted, non community-wiki answers of a minimum length are eligible