09-09-2010 05:12 PM
I submitted this support request to NI on 8/12/2010.
When I compile my LV 8.6 app in LV2010 I get this error:
"LabVIEW 10.0 Development System has encountered a problem and needs to close. We are sorry for the inconvenience."
I was told to do a "Mass Compile" of my LV 8.6 app in LV2010...this failed too.
I was then told to go to each and every vi and "Mass Compile" individually...after about the 50th vi this got old quickly...and it still didn't compile. I then sent NI tech support "my code". The good news is my LV 8.6 app didn't compile with LV2010 @ NI.
My LV 8.6 app compiles and runs great in LV 8.6. I don't want to be left behind with the newer upgrades and I want to move to LV2010. I have lots of LV8.6 code to maintain and I really don't have the time to debug all of my apps.
I was told this will be looked @ in LV2010 SP1.
One note...back up your LV8.6 data before you move to LV2010. Once your LV8.6 code is compiled in LV2010 you will not be able to go back to LV8.6.
I restored all of my LV8.6 code and I'm back working with LV8.6.
It's a tough call, do I stay in LV8.6 and get left behind?
Do I bite the bullet and try to debug this mess in LV2010?
I was told the compiler is completely different in LV2010. That's great, but one reason I have NI Maintenance Agreement is to keep updated with the latest software. I can't afford to re-compile LV code every few years. Like most people, maintaining my Apps with customer's revisions, and modifications is enough work. I don't want more work!
I was told LV2010 SP1 would likely appear in May or June of 2011. I'd hate to break out my old Turbo Pascal apps again...but hey...they still work! My NI maintenance agreement is due this month too, I guess I'll pay NI one more year, and see if they come up with a solution. But if NI doesn't fix this LV8.6 compile in LV2010 problem...I don't see any value staying current with LV software.
I found another Bug with LV2010...you are going to love this one!
There is a new "LV Update Service". Perfect! I like updating my LV software when new patches are available. When I click "update" the update spins over and over "Checking for New Version". I have let it run ALL day with no results...just sits and spins over and over.
OK, I know give NI a break! Yes, LV2010 has a new compiler...and Yes, I will renew my NI maintenance agreement. I just want NI to know failing to compile just one LV8.6 app in LV2010 is not a good idea for customer relations.
Thanks,
Doug
09-10-2010 11:16 PM
09-11-2010 09:52 AM
Doug,
That sounds frustrating- but lets look into it from a 10,000 ft perspective.
You have apps that do the job in 8.6 nothing wrong with that they do the job and will continue to do it!
You want to re-compile 8.6 code in 2010- WHAT is the benefit? that app is still limited to the capabilities of version it was developed in so building it in 2010 merely requires a RTE update. Absolutely ZERO enhancment!
your RE-use library is a different story. And perhaps it would be a good idea to look at possible improvements when new features become available?. the config file vi's were re-written in 2009. One likely source for the compile error
11-02-2010 06:43 PM
Hi Doug,
I'm the AE that helped you with the 8.6 to 2010 upgrade issue that you had. The problem that you were running into was fixed in the LabVIEW 2010 f2 patch. I tested the code that you sent in originally and I was able to open it without any issues.
Please download the patch and let us know the results.
Have a great day,
11-03-2010 10:14 AM
11-22-2010 10:25 AM
11-23-2010 05:10 PM
There is a LabVIEW 2010 f3 patch available now. You can try installing this to see if it helps your issue. The issue with the Update Service is a known issue. You can see how to resolve the issue here.
Brandon Treece
Applications Engineer
National Instruments