Reputation
208
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 9
Newest
 Yearling
Impact
~8k people reached

  • 0 posts edited
  • 0 helpful flags
  • 14 votes cast
Feb
23
awarded  Yearling
Feb
22
awarded  Commentator
Feb
22
comment A “sort of” Units of Unit of Work
@RobertHarvey I completely agree. My question did include if other patterns exist which did something like this, that I might be unaware of. If not, I won't be using the term UnitOfWork in my project (because it's really not). As for your example, my problem is much more complicated then that, but it still boils down to a series of items that need to all complete or all commit, it's only similar to a UoW.
Feb
22
revised A “sort of” Units of Unit of Work
added 8 characters in body
Feb
22
comment A “sort of” Units of Unit of Work
At the moment, I cannot foresee the need for a two-phase commit. Do you know of any examples that are similar to this? I can't really believe I'm the first person to ever do this.
Feb
22
comment A “sort of” Units of Unit of Work
Or the other way around. Say the save to the disk succeeds, but for whatever reason I am not able to create a record in the database, then the saved file would need to be rolled back (deleted).
Feb
22
asked A “sort of” Units of Unit of Work
Feb
13
comment Design caching system
the library is not an ASP.net library.. yes I said... it won't have anything to do with ASP.Net's cache, following this example in creating your own should be beneficial. Did read my post?
Feb
13
awarded  Editor
Feb
13
revised Should the expected value be hard-coded into the Assert
added 4 characters in body
Feb
12
answered Design caching system
Feb
12
awarded  Scholar
Feb
12
accepted Should the expected value be hard-coded into the Assert
Feb
12
awarded  Custodian
Feb
12
reviewed Approve Should the expected value be hard-coded into the Assert
Feb
12
awarded  Student
Feb
12
comment Should the expected value be hard-coded into the Assert
I'm having trouble trying to find an edge case where I wouldn't want to use the TestCaseAttribute, but it seems like an insanely proficient way to create tests.
Feb
12
comment Should the expected value be hard-coded into the Assert
It would look like [TestCase("Philips", Result = "Mr. Philips")] and return actual;.
Feb
12
revised Should the expected value be hard-coded into the Assert
edited tags
Feb
12
comment Should the expected value be hard-coded into the Assert
Ok, wow, using NUnit for the first time, and that seems completely the right direction. Assuming I can't use the TestCaseAttribute... :)