This week has been a killer in some ways.
I went into the office on Monday. I walked into a project in crisis. The features were there but the performance wasn’t. The BAs screwed up by not pushing the users to do a full mock-cycle. When the forecasting cycle rolled around last week, some of our users opened the app then closed it without doing any work in the tool. Users complained that the pivot grids were too slow to update after an edit. Performance in production was crap.
“Umm… Why did we hear about this issue over a month ago at UAT or during last-months mock-cycle?” Heads are starting to roll on that side of the fence.
Where am I going with this? Continue reading Slow down!
I’m building up a sample app that leverages the MahApps.Metro libraries. One of the challenges is setting the AppTheme and Accent colors dynamically. I looked through more than a few online solutions and none of them worked for me. Usually, the syntax was from an earlier version and didn’t match the ThemeManager object that I downloaded from NuGet (v18.104.22.168).
After comparing the sample app (v4.5) against my code in VS, I noticed the results from ThemeManager.DetectAppStyle() was always null in my app and valid in the sample app. Continue reading Setting Theme/Accent with MahApps.Metro
I have three different projects converging. They all need a more feature rich base class in the business layer.
I haven’t settled on a name for this base class. EntityBase? BusinessBase? BusinessObject? I expect something will stick in the near future.
You should notice that most of these interfaces are pre-existing Microsoft interfaces. ISupportUndo and ITrackStatus are inspired by Rockford Lhotka’s CSLA framework. The details are changed, but I really like the syntax to make the interface more readable. “I support undo.” I can’t think of a better way to express what the interface does. Can you?
I’m still working on the implementation details. I’ll share more once I have a stable sample app.