Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>What does this mean for those of us that used to write Windows Services to support our web apps?</p> </blockquote> <p>I think this a key scenario where you could be move away from a Windows service to using the continous running web site.</p> <blockquote> <p>Should we adopt this model? </p> </blockquote> <p>Standard development answer: Depends ;)</p> <blockquote> <p>What are the pitfalls? </p> </blockquote> <p>One issue I can see is the IIS dependency. If you need a service to run on a users machine I would not feel comfortable about asking them to install IIS just to run my service. Here I think the traditional model works better.</p> <p>Monitoring and tracking are major issues, but as you also point out this is solved by AppFabric. It is even better than what you get from the Window Service. However you have added another dependency which also will require .NET 4.0 and a relatively new version of Windows. I could also be wrong here, but my understanding is that AppFabric is not supported in production on client OS's. Which could bring in additional headaches.</p> <p>You will lose pause functionality in the continuous web site model too.</p> <p>Finally IIS killing inactive app-pools isn't the only way an app pool can recycle. Editing a web.config file causes it for instance, which may not be an ideal situation.</p> <blockquote> <p>the most useful being the ease of deployment. </p> </blockquote> <p>I also think development is much easier - in the past I have had a console app and a windows service so I can dev/test on my machine using the console app and then change it to a windows service when it goes out. Now dev/test is MUCH easier.</p> <p>A must read for this is <a href="http://weblogs.asp.net/britchie/archive/2010/09/08/death-to-windows-services-long-live-appfabric.aspx" rel="nofollow noreferrer">Death to Windows Services...Long Live AppFabric!</a></p>
    singulars
    1. This table or related slice is empty.
    1. POThoughts on running Windows Service type apps on ASP .NET 4 with StartMode="AlwaysRunning"
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJohnFx
    1. USRobert MacLean
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POThoughts on running Windows Service type apps on ASP .NET 4 with StartMode="AlwaysRunning"
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for posting your thoughts. I agree, I wouldn't look at developing a service in a web app if the requirement is that it needs to be installed on a user's machine. Regarding Windows Service development, I don't mind the environment so I don't know if it is easier/better. You mentioned you start with a console app for a Windows Service - I wondered what the reason for this is? I usually create the service and replace the ServiceBase initialisation stuff with alternative code in debug mode.
      singulars
      1. PO
      1. USRohland
    2. COFor a Windows Service project I normally do the following. Create a empty solution, add a class library, add a console app and reference the class library and add a windows service and reference the class library. In the class library I do all the real work, and the console app and windows service end up just being a way to call it. This means that while in VS, I can set the console app to be the default project and just hit F5 to test and debug. When I am ready for more real production or testing I can then just build the service ad all works the same - mostly ;)
      singulars
      1. PO
      1. USRobert MacLean
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload