Possible example what’s wrong with the Winforms application deployment experience?
Heh heh, slightly embarrassing, ain’t it, if it trips up a Wintel coding price winner.![]()
“UltraDynamo’s last major hitch revolved around the MSI installer required for submission to the Intel AppUp® center. Originally, Auld intended to generate the package from the InstallShield* Lite tool that comes bundled with Microsoft Visual Studio 2012. However, no amount of banging his head against the application helped him understand how to generate an MSI package directly. No matter what he tried, all he could get from the program was an .EXE installer, which the Intel AppUp® center wouldn’t accept. Finally, Auld did find a way to “double-install” into an MSI package, but the Intel AppUp center wouldn’t accept that either. Apparently, examination by Intel techs in a test environment revealed that “the shortcuts that the application installed weren’t announced shortcuts.”
“To this day, I haven’t got a Scooby what that means,” admitted Auld.
Fortunately, Intel came to Auld’s rescue. Tech support staff sent him an alpha version of a tool they used internally for app store packaging that relied on WIX* as its underlying toolset for generating installer packages.
“After working out how the Intel-provided app ran a couple of the WIX underlying commands to generate the MSI package, I took the XML file that the tool had created and used it as a foundation. I tweaked the internal XML nodes, got my shortcuts displayed on the screen, and then manually ran the WIX underlying commands to generate the MSI package. This then went through verification at Intel without any issue.””
If you won’t use US-International keyboard layout to type diacritics on Windows, 48 61 70 70 79 42 69 72 74 68 64 61 79…
… , that is to say (decode): Happy Birthday. You are 60 years old. For with ALT+NUM code, you essentially use ASCII (ok, to be more precise: High ASCII), a mapping of human language characters to computer binary numbers that was invented on June 17, 1963.
You can continue for another 5 years. Or if you don’t mean to be hard on your brain: Friends don’t let friends bypass US-International keyboard layout.
Request to download the Sanako Study 1200 licensing server, student and classroom name reset, program and source
Back to description for reset of server reset program.
Request to download the Sanako Study 1200 Recorder Installer source
(Please be advised that there is no compiled code download for this software program since any implementation is institution-specific. The source code (written in AutoIT) download is for demonstration purposes only and not ready to run without you making the necessary adaptations to your environment).
Back to description of sanako recorder install faculty program
How to test the LangLabEmailer
- The LangLabEmailer, when run, displays no GUI. To monitor:
- the progress, view the trace-listener.log;
- the results, view:
- “_sent” filenames in your assessment file store. NOTE: the LangLabEmailer will rename assessment files, by adding “_sent” to the end of the filename (for easy tracking;no deletions). If this is an issue for you, do not run it!
- “sent” items folder of mailbox used ( = mailbox of user logged into AD-domain-joined computer). NOTE: The LangLabEmailer will email assessment files from the language lab collection! (That is its primary purpose.) Specifically, it will send
- as you configured: within your campus email system (unless your campus mail administrator allows mail forwarding),
- as you configured: from the campus mail account you have the right to send from (I have the right to send ca. 3000 messages per day; you may want to inquire with your MS-Exchange admin about your limits),
- as you configured: from the student collection file share classroom data (which has special, relaxed FERPA rules),
- per its design – which is primarily based on file ownership which itself is based on who logs in on the originating lab computers and the digital audio lab software’s saving rules for pair and group work, but also by making some honest guesses about the intended recipient, based the file name and, as you configured, the list of teachers using your lab (since from experience these also happen to be logged in for students at times) – , primarily to the presumed originator and to her teacher (and in special cases, as a fallback, to whoever you configured as language lab admin).
- If this sounds a tad scary: just start with configuring
- a few “dry” test runs (no sending, no renaming, just logging what would happen)
- then some limited test runs (small time window and dummy files)
- and examine the results which the langlabemailer logs for you in either mode, and you will likely find, it is not scary.
- Next: Run. Or up:Langlabemailer table of contents.


