Yup, Upgrading LabVIEW versions takes a day.
The "Process" today is:
Yup, about a day of watching paint dry...........mass compiling, ignoring warnings etc......
"MyLabVIEW" would find all of those customizations and import them to the new version!
Not to mention any vi.lib edits (such as changing default Accessors to be called Get/Set instead of Read/Write).
Is there an exhaustive list of what such an implementation would need to take account of?
It would be majorly cool even if the list of modules to install could be selected from a file created from a previous installation.
Even more impressive would be keeping a snapshot up to date of a current installation allowing to clone that environment on a new PC at any time.
The possibilities are endless.... Kudos.
Try adding LabVIEW Real-Time and LabVIEW FPGA to the list, if you also use these. We're now talking about 2 days.
As I recently had my laptop crash and got the joy of installing 5 versions of LabVIEW back to back, I would really have enjoyed this. Is is me or is it ironic that the spell checker on here flags LabVIEW as misspelled?
If you like the idea, then be sure to click on the Kudos button to register your vote for it!
A link to help define the essential MyLabVIEW requirements
Feel free to post your My-Options
I'm sure you already know of this solution I'm going to suggest, but others may not.
I have made the install process a little less painful. I have combined the 3 developer suite DVDs, the additional FPGA tools, and device drivers into one folder. So there isn't disk swapping when installing. I just choose the products to install and say "go".
Secondly I make a VIPC using VIPM which contains all the OpenG packages I want, and all the internal reuse packages I want. This means no download time and just one file to click and tell VIPM to install.
One of the internal reuse packages installs quick drop shortcuts and other functions.
One of the internal reuse packages configures LabVIEW.ini to have the palette shown the way most developers like. It also does other settings like labels on the left for controls right for indicators, setting terminals not as icons, etc.
One of the internal reuse packages installs extra glyphs for the icon editor.
One of the internal reuse packages installs templates and example projects.
This means all I do is choose the products to install, then install the VIPC. These two steps aren't fast by any means but having no need for human intervention other then these two steps makes the process much faster. I'd say I can setup a PC with LabVIEW, FPGA, Device Drivers, and have it setup the way I want in 3 hours while I work on other things, go to lunch, or go home.
Unofficial Forum Rules and GuidelinesGet going with G! - LabVIEW Wiki.12 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
I believe this is a duplicate of the following posts, even though you list more items to be automatically configured.
Don't hold your breath to see this done anytime soon. I suggested it first a little over four years ago after having the same day you described above, and still nothing.
I would not limit this suggestion only to upgrading. Having an opportunity to move such "personal adjustments" between computers would be nice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.