Earlier, I posted on how to build CINs for LabVIEW using VS.NET 2005. However, after a lengthy thread over on the NI devzone forums, I realized I forgot to add an important note...
When you distribute the CINs to a machine w/o VS.NET 2005 installed on it, you need to ensure you install the C/C++ runtime libraries from VS.NET. There is a handly installer here that does it for you here.
This is actually a requirement for any CIN (installing the C/C++ runtime). It's just that most applications on Windows also need them, so more than likely they've already been installed. VS.NET 2005 is so new that you'll often be the first application that needs them. I'm sure that'll change with time, but for now...
Finally, the wrapping has come off. Today during the NI Week keynote (which started at 8:20am...go figure), we announced LabVIEW 8.20 - the 20th anniversary edition of LabVIEW (in case you were wondering what happened to the 8.1 version). And most importantly - it's released. Yes, we sent the image off to duplication earlier so it's now just a matter of awaiting the physical kits...no vaporware!!!
Probably the most talked about feature in 8.20 is the new support for LabVIEW classes - yes, that's right, LabVIEW now has object-oriented programming built in. To learn more about it, check out the link above, or you can listen to the podcast on it.
Of course, the most important feature is the new Web Service Import Wizard. Why? Because my team wrote it...honestly, I don't know what to do with you sometimes. A quick clarification - there are still some marketing points that refer to it as the .NET Web Service Import Wizard. That was the original name, before we pointed out that it could import a web service written in any language or running on any OS - it's only the client code (that would be you) that has a dependency on .NET (its what we use under the covers).
Anyway, lots of new features, lots of improvements, lots of goodness and love and peace and puppy dogs, etc. etc. Check it out and feel free to drop your thoughts on it...unless it's on the OO design debate...I don't think I have enough storage space :)
Kinda dropping this link on the new .NET 3.0 Framework for my own future reference, but it's a handy little paper. Much more information than most need to worry about (especially since 3.0 ships as part of Vista), so don't panic if it seems like a lot. For most people, you only need to download and run the .NET 3.0 framework, just like previous versions.
Okay, so it's been a lot longer between the last post and this one than I had planned. Life does that to you sometimes. I'm afraid that I'll also be even more sporatic over the next several weeks as I have (a) vacation, (b) business trip and (c) NIWeek 2006...
But, let's talk now about the issue of security when using ASP.NET and LabVIEW via the ActiveX interface.
Previously, I talked about using the LabVIEW ActiveX Server interface from within your ASP.NET application. I mentioned that the wonderful world of DCOM security, by default, would prevent you from calling LabVIEW through this interface. In this post, I'll explain how to configure the security settings to get this working.
WinFX, for those that don't know, is basically the successor to Win32. It's a .NET API framework for some of the new techologies coming out of Microsoft. The three big names in it for this release are Avalon (aka Windows Presentation Foundation), Indigo (aka Windows Communication Foundation) and InfoCard. However, there are several other APIs that have been added to provide more Win32 abilities from within .NET.
However, there seemed to be some confusion over the difference between the .NET Framework, which has a bunch of .NET APIs, and WinFX, which has a bunch of .NET APIs. So it was decided to drop the WinFX name and go with just the .NET framework. Thus when Vista ships, what is available is .NET 3.0 - not WinFX. But this is pretty much a naming change - what is going to be available is the same as before.
An interesting note is that Vista is going to come pre-installed with .NET 1.0, 1.1, 2.0 and 3.0 - so you're ready to .NET the night away!
I'm happy to announce that we (as in National Instruments) have set up a new Community Site for code samples and examples. I'm going to try migrating my examples over there, but I'd love to see everyone give this site a try.
Note that the site itself is still in Beta, but that doesn't mean you'll need to resubmit once it's "released" - everything you do there should be maintained over the beta to release transition.