PaulG. Posted February 15, 2011 Report Share Posted February 15, 2011 I've done my fair share, uh, um, more than my fair share of bitching about LV lately and decided to sign up for beta testing. My current project is a cRIO system we intend to access remotely via FTP and I'll be doing most of the beta testing using this project. I would like to beat the snot out 2011. What better place for direction than here? Thoughts? Experiences? Advice? Thanks in advance. Quote Link to comment
Jarrod S Posted February 15, 2011 Report Share Posted February 15, 2011 Do note that generally drivers like NI-RIO are not available in the first Beta. Their beta versions usually arrive for the second Beta. So if you sign up now, you'll only be able to test out your host-side app to start with. Quote Link to comment
Daklu Posted February 15, 2011 Report Share Posted February 15, 2011 Advice? Install it in a virtual machine. Quote Link to comment
ShaunR Posted February 15, 2011 Report Share Posted February 15, 2011 I'm still waiting for the 2009 SP2 Go Paul. 1 Quote Link to comment
PaulG. Posted February 15, 2011 Author Report Share Posted February 15, 2011 I'm still waiting for the 2009 SP2 Go Paul. Quote Link to comment
jgcode Posted February 16, 2011 Report Share Posted February 16, 2011 I've done my fair share, uh, um, more than my fair share of bitching about LV lately and decided to sign up for beta testing. My current project is a cRIO system we intend to access remotely via FTP and I'll be doing most of the beta testing using this project. I would like to beat the snot out 2011. What better place for direction than here? Thoughts? Experiences? Advice? Thanks in advance. I am only guessing here - when you say "we intend to" means you haven't started coding the project yet but will start in LabVIEW 2011??? I guess it depends on you critical the job is but I wouldn't do this at all: If you run into any issues (and from experience I have had are more issues with RT/FPGA than Desktop LabVIEW) then you have no where to go. If you develop in a version you consider stable and you know what you have to do works, then you can always upgrade at some point, test it, then rollback using SCC if needed. If you develop code that depends on a feature in 2011 and you get burnt somewhere else you may find yourself in a tricky spot. 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.