Hi Rob,
Some recent refactoring in the ms sql data layer introduced a new SqlParameterHelper class. In the past all the methods in dbPortal.cs had big nested if statements with different parameter assignment syntax used depending on whether parameters were cached. If cached, the parameter types are retrieved from the db instead of defined in code.
The new helper class encapsulates it and asserts whether the parameters defined in code match those retrieved from the db so it is finding bugs that previously would only have come up if caching was disabled. In this case for example the paramter was defined in code as Direction.Output but the param retrieved from the db was Direction.InputOutput. I don't think in this case it would have thrown an exception at runtime even if the caching was disabled, but the debug.asserts are failing and pointing out places where code should be corrected. In this case I'm chagning the code so it defines the param as .InputOutput
I will have this one fixed in svn trunk by end of the day. Please do let me know any others like this you encounter while debugging. A few of these have come up already, they will only come up while debugging, the release files are not affected by debug.Assert errors.
Thanks,
Joe