35 replies to this topic

[Phillip Brooks]

http://zone.ni.com/w...doc/p/id/wv-157

[Tim_S]

Phillip Brooks, on 29 July 2011 - 12:48 PM, said:

http://zone.ni.com/w...doc/p/id/wv-157

Hrm... and there is a download link to LV 2011... well, there goes my weekend.

Tim

[WireWarrior]

I like some of the new features!

Jason

[Jordan Kuehn]

Here's a list if you don't want to watch the lengthy AE video:

http://www.ni.com/la...tsnew/features/

The 13 user suggested items seem quite nice.

[jgcode]

I think the stability and performance features of LabVIEW 2011 get me most excited

[Phillip Brooks]

jkuehn, on 29 July 2011 - 02:17 PM, said:

Here's a list if you don't want to watch the lengthy AE video:

http://www.ni.com/la...tsnew/features/

The 13 user suggested items seem quite nice.

It was still showing LV 2010 when I posted this morning. The pages must be slowly rolling over to 2011 versions.

[Val Brown]

And exactly what is the download link?

....just joking. Thanks for the link. I've been waiting for it.

Edited by Val Brown, 29 July 2011 - 05:18 PM.

[Jordan Kuehn]

Phillip Brooks, on 29 July 2011 - 05:10 PM, said:

It was still showing LV 2010 when I posted this morning. The pages must be slowly rolling over to 2011 versions.

Here's a tease. NI must like me more

Edited by jkuehn, 29 July 2011 - 05:33 PM.

[gleichman]

I haven't seen it mentioned anywhere, but it looks like Developer Suite Core added three toolkits.

• VI Analyzer Toolkit
• Desktop Execution Trace Toolkit
• Unit Test Framework Toolkit
  

I guess I should have bought VIPM instead of DETT.

Edited by gleichman, 31 July 2011 - 03:02 AM.

[Tim_S]

Tim_S, on 29 July 2011 - 02:10 PM, said:

Hrm... and there is a download link to LV 2011... well, there goes my weekend.

Tim

Well, I've got LV2011 downloaded, installed and configured. I mass compiled my current project, loaded the project and proceeded to send in my first SR for LV2011. Uh oh...

I received a pop-up on loading the project stating:
Compiler error. Report this problem to National Instruments Tech Support.
Dynamic IUse Node has no reference VI to call. Node = 0x0000000B

Tim

[ShaunR]

New crash reporter



But it definitely feels more responsive than 2010.

Edited by ShaunR, 31 July 2011 - 07:37 PM.

[ShaunR]

List of bug fixes in LV 2011

[jgcode]

ShaunR, on 01 August 2011 - 06:18 AM, said:

List of bug fixes in LV 2011

It's cool to see issues fixed that: I've posted (got CAR) or have affected me. One of the more interesting fixes for me is:

214860 — Build path too long when building application

This has been a problem since introducing the new exe structure in LV2009 (which was an awesome new feature). I look forward to looking at this in detail.

[mje]

I'm most excited about the apparent IDE speed increases. Though this little diddy is also great news:




In particular:

Execution Details
This node exhibits the following execution behaviors:

• Does not require the user interface thread to be idle

[neBulus]

mje, on 01 August 2011 - 01:36 PM, said:

I'm most excited about the apparent IDE speed increases. Though this little diddy is also great news:

abcr.jpg


In particular:

Execution Details
This node exhibits the following execution behaviors:

• Does not require the user interface thread to be idle

Ding ding ding ding... we have a winner ... in my book.

Ben

[mike5]

Is there a way to "mix" versions 2010 and 2011. I tested some things today, and afterwards LV2010 didn't want to open my project anymore. Nothing that a "SVN revert" cannot solve.

But what does it do to VIs? Anyone has any suggestions how to use both versions at the same time? Or is don't the only option?

Br, Mike

[Val Brown]

The VIs are recompiled by 2011 and that is why they need to be reverted separately instead of just being opened in 2010.

[Tim_S]

mike5, on 02 August 2011 - 10:04 AM, said:

But what does it do to VIs? Anyone has any suggestions how to use both versions at the same time? Or is don't the only option?

Yea, don't is the only option. It extends beyond the source code from my experience to where you have to compile a LabVIEW DLL in the same version of LabVIEW you are using to call it.

Tim

[Val Brown]

Each version will look for relevant DLL from NI in the resource folder under the version's executable path -- unless you've specifically set any of the Call Function Nodes to other particular locations for the DLLs.

If you use SVN you can always commit the 2010 version and name that rev accordingly the, when you want to open THAT rev in 2010, open 2010 first, then load the lvproj file from within that interface. If you just double click on the lvproj or VI file the last loaded version of LV will load and try to open the file.

[Ad Dekkers]

Does anyone know when the new development suite will be available?