The goal was to handle recurring donations. Every month, Suzy wants to donate $10 to Cool NPO. It’s not a pledge, in that she’s not dedicating herself to $120 for one year. Just $10/month. (Forever! Bwua-ha-ha!)
A word to anyone doing an eTapestry API integration for a client who uses Blackbaud Merchant Services: you may have an eTapestry sandbox, but you don’t (and can’t) get a BMS sandbox account.
So how do developers test their API interactions? According to the BMS account rep I spoke to, they do it on the live system. With live credit cards. From the get-go.
So I’m in a D&D 3.5 campaign now. And I’m playing a Druid, which is kinda exciting–it’s the first time I’ve played a Druid at a high enough level that I can shapeshift, and I just tipped 5th level on Sunday. (Campaigns always fizzle out early…)
Anyway, the campaign is a hodgepodge of standard D&D and Sandstorm, and summoning restrictions by the GM mean that my spell list involves a fair bit of swapping out that’s a little annoying to manage. For instance, I’m using Sandstorm’s “Desiccate” instead of “Summon Nature’s Ally II”, since I can’t summon.
Since Druids are the type to prepare a few spells per day from a large list of available spells, I needed a quick way to see all of my available options without flipping through two sourcebooks and my swap list at the table. Then I wanted to avoid having the jotted down short-hand description of the spell that I refresh every “day” as I try out new spells.
Pain in the ass.
A bit of Googling lead me to conclude that with the advent of D&D 4e, many of the 3.5e resources… disappeared. And by disappeared, I mean:
All files withdrawn at the request of Wizards of the Coast.
Talk about taking a large bite.
In the interests of pushing my .NET knowledge, I began migrating the Geist character sheet project that I’d started in Django to .NET MVC 3. I hadn’t done MVC in .NET since MVC 1 was beta’d, but hey, MVC is MVC is MVC. Right?
So in the interests of making things more interesting and more testable, I decided to dive into the Entity Framework 4. My beginning read of POJOs in Action, along with my previous experience with .netTears–I mean, .netTiers–had me generally familiar with the concepts of entities, contexts, and repositories.
Kicker is, POJOs is just a book (and one I’ve barely dived into), and .netTears uses code generation, meaning I could get away with treating it as just a very hefty ORM in the applications it was in. Generate and go.
Getting my fingers in it was a whole ‘nother experience.
wsdl error: XML error parsing WSDL from https://sna.etapestry.com/v2messaging/service?WSDL on line 1: Not well-formed (invalid token)