Couldn't find anything similar when I searched so thought I'd throw this out there for use in file names in a Windows file system:
DateTime.Now.ToString ("yyyyMMddHHmmss")
Will output "201001312359"
Add a ".txt" or ".dat" if you're hard-core and you're all set.
You can programmatically determine if the SPPublishingPage you're dealing with is in a published state by retrieving the SPFileLevel of the page's corresponding SPFile:
if (page.ListItem.File.Level == SPFileLevel.Published) …
You can also access this through the PublishingPage.ListItem.Level property.
The same SPFileLevel enumeration will also indicate if the page is in draft mode (checked in but not published) or checked out but in my experience this property will return SPFileLevel.Published or SPFileLevel.Draft more often than not.
To determine whether the page is checked out, use the SPFile.CheckOutStatus property in WSS 3.0 or the SPFile.CheckOutType property in SP2010. Any value other than None means the page is checked out.
There's a subtle distinction between SPSite.AllWebs and SPWeb.Webs to be aware of—and yes, despite this being the SharePoint API we're talking about, it's more than just a naming oddity!
SPSite.AllWebs returns the immediate child webs of the site collection and all of their child webs (in other words, all webs recursively within the site collection); SPWeb.Webs has a much narrower scope and only returns the first level child webs immediately below the SPWeb object.
So what does this mean and how does it benefit you? If you're writing code that recursively walks the site hierarchy using SPWeb.Webs, you may be able to avoid the overhead by simply using SPSite.AllWebs. Recursion is fun and all but it adds complexity where it may not be warranted.
