crelf

I got my ticket! PS: If that Brian Powell guy says I'm paying for his ticket, he's a dirty rotten filthy stinkin' liar!

What do you mean by "how to test"? I agree. If those questions/answers were in the CLD or CLA, then I'd ask for them to be changed, but this test is for a completely different scope. Afford me a story: When I was in my first chem class in college (I was a science-physics major), the lecturer asked us to draw a model of a sodium atom. After some time trying to remember how many electrons it has, and the packed orbital limits, most of us came up with the old nucleus surrounded by co-axial rings. He showed a slide that looked just like that ("whew!"), and then said, although it's certainaly a model that was enough to get us through high school, it was time to abandon it for something closer to the truth, as the old model wasn't accurate enough for what we needed to learn now. So, should the high school ciriculum be changed to teach everyone the latest, greatest and most complex model of the atom? No - because, for the intents and purposes of high shcool, the model that we were taught is just fine. Same goes for tests like this - if you only ask questions that the most savvy architect knows the real answer to, then you're defeating the purpose of the quiz. That said, if there's something blantantly wrong in one of those quizes, or you disagree with the scope, then feel free to ping NI training about it. We've had success in having quizes updated in the past.

I'll kudos your idea if you kudos mine: http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/Add-quot-Project-Globals-quot-and-or-quot-Workspace-Globals-quot/idi-p/1148493

If you ever do work out the pattern, it'd be nice if it was added to the LabVIEWwiki.org.

Can't argue with that. IMO Zune's biggest downfall was that it wasn't marketed by Apple.

Although I worked on the team that designed and built the EOL testers for the Zune family, I have no internal knowledge on this - this is purely my own speculation: I like to think that MS "did" the Zune for a number of reasons, not only to try to make $ in that product domain. My gut feel is that a lot of what they learned during Zune has gone into the Windows phone, and part of me beleives that the Zune was, at least in part, a precursor to the phone by design.

Ok, we're confusing terms: "Base" = Full (it's got everything including all the other installers), then "Upgrade". Can you repost using those terms, because I' mnot understanding what you're trying to say when we mix the terms.

A side note: when I'm in this situation, I create two installers: one base installer for new users, and an upgrade installer, and put them side-by-side on the download page, with the full one first - and I make sure I name them so it's obvious which one's which, as well as list the file size (so those with the full are generally forced to look twice). This means that people that don't read the instructions most often download the first one (the full), so even if they already have it installed, there's no harm done (other than them having a larger download). As for your actual question: Sure, you can create a launcher that looks for the essential components then error out and close should they not be there, or dynamically load the main app if all is well. It's a good place to put custom license control stuff too.

I prefer to use the registry. We have reuse VIs that read application ini files in their application folder, then when MS really started locking down Program Files, we made drop-in replacements that work with the application's entry in the registry. Plus, that gives us a much easier way to overwrite or add keys outside fo the application's installer (eg: say an installed instance includes a couple of our products + a custom OI: we can install the standard stuff and keep it encapsulated as products, then overwrite any important custom stuff with the custom OI's installer) - works great iff you install stuff in order (there's something not quite right about LabVIEW's installer when it comes to registry keys).

"face heart"? Awwwww So I wonder if this would make a nice labviewwiki.org entry? Maybe it could be expanded to include antonyms that are specifically LabVIEW-centric?