Sorry, couldn't reply earlier, internet connection problems...

Anyway, Doh! Obviously I was so convinced the method would do what I wanted that I hadn't read it properly! My bad. Though I am curious about what the purpose of GetContentForRelease() is? Wouldn't it always return nothing?

Anyway, based on the source code and your help I managed to come up with this quick razor test that seems to work:

RepositoryFactory _repositoryFactory = new RepositoryFactory();
IDatabaseUnitOfWorkProvider _uowProvider = new PetaPocoUnitOfWorkProvider();

using (var repository = _repositoryFactory.CreateContentRepository(_uowProvider.GetUnitOfWork()))
{
    var query = Query<IContent>.Builder.Where(x => x.Published == false && x.ReleaseDate >= DateTime.Now);
    var contents = repository.GetByQuery(query);

    <h1>Contents @contents.Count()</h1>

    foreach (var item in contents)
    {
        <p>@item.Id @item.Name @item.ReleaseDate</p>
    }
}

So that's pretty cool, as I never knew you could so such nicely typed queries with PetaPoco.

Though isn't there any method to do this already? I presumably the built-in Umbraco scheduler must call some method to get events that have been scheduled to publish? Am I reinventing the wheel? 

Cheers!

The background service / scheduler that publishes Content items looks for items that has to be publish now or should have been published by the time it checks.

Imagine you create a content item that has to be published at 12:00 tomorrow. When the scheduler looks for content it has to publish today at 12:00 it should not get a list of items to be published in the future. Instead when its tomorrow at 12:00 or 12:01 for that matter it will get that one content item that it has to Publish now.

Makes sense?

/ Morten

Ahhh, yes, that makes perfect sense. So basically the scheduler will be running at an interval in the future and then needs to look back to see all the content that should have been published in the interim. (Thank God you guys write the logic and not me :p)

Just to explain a bit what I'm trying to achieve to canvas your thoughts:

The problem I have is that we have a client who needs to schedule things to publish in the future to an exact fidelity - to within a minute (they sell event tickets that need to go on sale at, say, exactly 9am and a not a minute before or after). We've found the Umbraco scheduler not quite this reliable (which is understandable given the web context it runs is).

So what I was thinking of doing was writing a quick controller action that would get a list of the content that needs publishing and then publish whatever needs to be done. And then creating a quick console app that calls this controller (via it's URL with a secure token) and then scheduling this using Windows Task Scheduler to run every minute (or whatever) on the server.

• So scheduler runs every min or 30 seconds
• Scheduler calls console app that makes an HTTP request to the controller (within Umbraco context)
• The controller then calls GetContentForRelease() and publishes any items that come back

is working on a reply...