MartinMcD Posted April 29, 2010 Report Share Posted April 29, 2010 Hi there, Our company is shortly going to be making the jump from 8.2 to 2009 (yipee). I'm just being asked if there are any known issues either with making the jump or with 2009 itself. Any tips? Thanks very much, Martin Quote Link to comment
asbo Posted April 29, 2010 Report Share Posted April 29, 2010 NI maintains a list of known issues for many of its products. Can't comment on the 8.2->2009 growing pains, though. Quote Link to comment
Phillip Brooks Posted April 29, 2010 Report Share Posted April 29, 2010 We only upgrade every few years. Our last upgrade was from 7.0 to 8.6. We used the release notes combined with an add-in to VI Analyzer called the VI Upgrade Analyzer. I think that VI Analyzer may be licensed in LV 2009 as a separate package. Upgrading to the Latest Version of LabVIEW LabVIEW 2009 Upgrade Tests Quote Link to comment
Yair Posted April 29, 2010 Report Share Posted April 29, 2010 I think the biggest annoyance was with the report generation toolkit. Many people made copies of its VIs in previous versions to do stuff it didn't do itself. In 8.6 NI changed the toolkit to be a class hierarchy, thus breaking all that code and requiring you to fix it. If you have such code, be aware of this. The same thing was done with the configuration file VIs in 2009, so if you modified those, you'll have to fix that too. 1 Quote Link to comment
LogMAN Posted April 30, 2010 Report Share Posted April 30, 2010 (edited) We have used LV2009 for one large project and never since. That was because of many failures. For instance: Error in Line XYZ in MemoryManager.cpp. LabVIEW crashed with this error every 2-3 runs. Also after we updated to LV2009 SP1... We switched back to LV8.6.1f1 and everything works fine. Also the VI and EXE files were larger (LV2009: 15Mib / LV8.6.1f1: 12Mib) We use almost everything of LabVIEW, except of Mathscript and Remotepanels. Our applications have about 200 - 300 self made VIs. We are in need of better multicore processing, but LV2009 is to unstable. But I think, wether to use LV2009 or not depends on your needs. If you do parallel computing and need more performance using multicore processor, LV2009 might be a good choice. If you only do "normal" stuff, LV8.2 or LV8.6 / LV8.6.1f1 is the better choice for now. Install LV2009 on one computer, load some of your projects and do some tests. (Also perform some errors!!!) Greetings, LogMAN Edited April 30, 2010 by LogMAN Quote Link to comment
jgcode Posted April 30, 2010 Report Share Posted April 30, 2010 Hi there, Our company is shortly going to be making the jump from 8.2 to 2009 (yipee). I'm just being asked if there are any known issues either with making the jump or with 2009 itself. Any tips? Thanks very much, Martin Other have mentioned some negatives, I can think of a few positives (off the top of my head): Classes: Oh, man. If you like using classes, you are going to love 2009. 8.2 was when they were launched and they were a bit raw. In 2009 they are quite refined. Executables: You also have a new build model for exes which is nice So if you use libraries (.lvlibs, .xctls, .lvclass) your build will be neat - no more external files Project: The project is much better, more functionality at your fingertips etc... For example - I can really do some cool this when creating source distributions Cheers -JG Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.