Service Factory Hands-on Lab

At some point in the future I'll provide more information about what you'll find in these hands-on labs. But rather than force you to wait until I've worked out my prose ...

Learn

Download

Known Issues

  • WCF
AddExceptionShieldingEntryActionFixture does not pass. Error (GenericArguments...)
This problem seem to be related with the probing references of ExceptionShielding binary.
So the solution that fix this is to set the asm location to the test folder where all the required binaries lives.
Go to the PopulateArguments function and change line 90 with:

action.ExceptionHandlingAssembly = ConfigurationLoader.GetConfigurationFilePath("Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll");

After this change, both tests should run sucessfully.

Last edited May 29, 2009 at 9:48 PM by donsmith, version 13

Comments

hernandelahitte Jun 5, 2009 at 11:16 PM 
The CohoWinery was replaced by BlueYonder.

assankhan Jun 2, 2009 at 1:45 PM 
the above download link is wrong http://servicefactory.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=7846
it gives the BlueYonder project not the CohoWinery

SirEel Nov 9, 2007 at 4:26 AM 
The zip file contains .csproj files that can't be extracted in Vista with Windows Explorer because their names are too long. For instance a number of files named "BYA.Mfg.SCM.Svc.WCF.BusinessEntities.csproj" are buried many layers down in folders with similarly prolix names. I'm trying to extract them on NTFS. Perhaps WinZip or some other $$$ program can extract these files, but I can't find a way to do it with plain old Vista. I'd appreciate if someone knows a workaround. Is it not a best practice to use short file names?

mikeliu88 Aug 6, 2007 at 3:57 PM 
Another hiccup:
dte_CardExpiration is added twice by the wizard. You have to manually delete the first one from these 2 places:
ClubMemberInsertFactory.MapDbParameterToBusinessEntityProperty
ClubMemberInsertFactory.ConstructInsertCommand

mikeliu88 Aug 6, 2007 at 2:32 PM 
There is an error in the cmd (sql file) to create the Coho database. The workaround is to run the same cmd twice if you don't want to correct the sql file.

Below is the error message from the first run:

Changed database context to 'CohoWinery'.
Msg 208, Level 16, State 1, Server SELIU06877\SELIU06877_2005, Procedure MembersInTasting, Line 3 Invalid object name 'dbo.cwt_TastingMembers'.
Msg 15135, Level 16, State 8, Server SELIU06877\SELIU06877_2005, Procedure sp_addextendedproperty, Line 37
Object is invalid. Extended properties are not permitted on 'dbo.MembersInTasting', or the object does not exist.
Msg 15135, Level 16, State 8, Server SELIU06877\SELIU06877_2005, Procedure sp_addextendedproperty, Line 37
Object is invalid. Extended properties are not permitted on 'dbo.MembersInTasting', or the object does not exist.
Finished!