I like shiny new things. Apparently I’m attracted to flashing lights aswell, which explains the working in IT.
FWIW, in my mind, I was justifying the use of .Net4.5 and access to the new parallelism functionality that is available.
Because I like new toys, and because I didn’t really have a hope of getting budget approval for an Infor upgrade of Smart Office, I figured I’d do some research, use my DR environment and test doing an upgrade by myself.
During the research I came across two major stumbling blocks.
1). Our M3 UI Adapter wasn’t supported under 10.1
2). Smart Office doesn’t get upgraded, it gets replaced <sigh>
So, pouring over the documentation in my usual manner I looked to see if I could run multiple grids against a single BE and couldn’t find an answer – this may well have been because there wasn’t a section that said “Running Multiple Grids against a Single BE” but that’s a conversation for another day.
I caved and flicked a quick message to the resident Infor techy and asked “Can you have multiple grids against the same BE” which resulted in a resounding (ok, somewhat paraphrased) “not sure”.
This meant I was going to have to take a risk and potentially hose one of my environments and then get someone in to fix the issue. Not really something that appeals to me but I was planning on using my DR environment to test against. The beauty of this is, AS400 aside, the supporting services are all virtualised and get refreshed each night. Plus they have snapshots that I can quickly and easily revert back to.
As it turned out, doing the upgrade on my DR environment turned out to be a real drama that was going to absorb far too much time so I took a calculated risk and decided to try against our TEST environment. Our TEST environment has only been used a few times over the last 12 months and most people test in DEVE – don’t ask.
To make me more nervous, we have our production AS400, it runs our DEVE, PROD and TEST environments (we are a small company, so even with the AS400 we run, it’s more than capable of hosting the lot and more). Likewise, our Smart Office server has three environments, DEVE, PROD, TEST.
Upgrading one environment shouldn’t affect any of the others, but it really just didn’t feel good.
My plan of attack became:
1). Upgrade the M3 UI Adapter (10.0.1.0 to 10.2.1.0)
2). Ensure that Smart Office 10.0.5.2.x still works without issue
3). Export the Smart Office settings using the MangoAdminTool
4). Uninstall Smart Office 10.0.5.2
5). Install Smart Office 10.1.1.0.x
6). Import Smart Office settings and Test
7). Congratulate myself heartily for my death defying feat
Continue reading
or the cross on the close. I couldn’t find anything similar in the images. It turns out that I was looking in the wrong place. And to my surprise I discovered the Mango.DesignSystem namespace and the goodies it contains.



for my replacement of a modification, I wasn’t really sure which icons I should be using.