Profile cover photo
Profile photo
Paul Brown
Paul Brown's interests
View all
Paul Brown's posts

Post has attachment
I finally got around to writing up my experience of The Legend of Kremlo the Slann from back in March. As an introduction to Lustria it has its place, and there are some interesting possibilities mixed in there, but I wasn't too impressed with the battle scenarios themselves which seem very one dimensional.

Maybe that's just me... so who else has played this through, and what did you think?

Post has attachment
Various cool stuff on this community and the forum have got me thinking about 40K - but I still have an underlying issue with sci-fi gaming that I struggle to ignore the "sci" part. So how to make 40K more medieval? Here's some ideas, see what you think.

Post has attachment
Chiming in a little late on the "projects for this year" theme. Is it wrong to set a target quite so out of touch with reality?

Post has attachment
I enjoyed this - interesting to take a classic D&D trope, think about it some more (perhaps adding a much-needed dash of cynicism) and end up with WFRP!

Post has attachment
Possibly complete jibberish (and certainly far too nerdy), but it'd be interesting to hear any feedback on my thoughts on the DotR Reikland map / gazetteer versus what I understand is the modern canon version. Especially from +Andrew Law as he seems to know more about this than is healthy   :)

And I realise I could have just said "I'm using the DotR version, I like how sparse it is"...   :)

Lifecycle management for SharePoint Designer 2010 workflow

I have a Publishing site (single site collection) for which I've developed a reusable workflow associated with the Page content type in our development environment. I can then save this as a template, import into our staging and the live environments, activate, associate and I'm good to go. However, I'm unsure of a couple of aspects of the lifecycle –

The workflow in our development environment is different to the staging / live (i.e. it's not a feature). Am I better off running up a second site collection to develop in, effectively to act as the “source code repository” so that I can then import the developed workflow into our main development site in the same way that it will be imported into our staging and live? I can then test properly within development (e.g. I know that the association columns are from the feature) and also develop the script to automate activation of the feature in the various sub-sites in the site collection.

What's the best way to ensure this feature is activated in any future sub-sites we create?

What's the best way to upgrade the workflow in future should it be necessary? There's a reference here - - to creating new features side-by-side with the old one then modifying the workflow associations, but does that apply to imported SPD workflows or just Visual Studio ones?

Any answers would be helpful but also references / books for me to read for fuller background would be most appreciated.

Post has attachment
How civilised is your Reikland?

Post has attachment
Playing as Skaven - has anyone tried it? What good source material is there out there?

I'm creating a survey where one of the questions is the respondant's office location, with the complexity that regional managers might answer for any office in their region. I'd like to default it to the probable correct value (choice), so that users can select another office in their region if filling in on behalf of a colleague, and regional managers can select within their region.

It seems like the sort of thing that a SharePoint 2010 list should be able to handle (and even the cool but slightly irritating sub-set of a list you get with surveys). But I can't get my head around the solution.

The offices could be implemented as a taxonomy if that helps, although again the coolness of managed metadata fields seems to often be hampered by their limitations.

Any thoughts much appreciated!

Post has attachment
Looks really interesting. Never mind the license cost, I've seen what hard work InfoPath can be both from a user experience and a functional point of view. One to go on my (ever increasing) "to investigate" list... Although conversely there's the support overhead for future maintainability in going down a non-standard route.

Anyone tried anything similar, or have feedback on this route?
Wait while more posts are being loaded