06-29-2011 06:57 PM
pdenton wrote:We are currently targeting v9.1.1 (that is the first Service Release for v9.1) for a potential fix.
We are currently targeting v9.1.1 (that is the first Service Release for v9.1) for a potential fix.
I love it: We are now getting plans for releases which update releases that have not yet been released!
4 weeks ago
I'm told that this was fixed in 9.1.3 as a result of moving to moving to .NET4. Check out
SR-11052010-0014 in the release notes.