LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

visual studio .net 2003 & dll creation

Hi,

I'm a newbie so bare with me.

I'm walking thru "LabVIEW: Using External Code in LabVIEW" and since I'm using a later version of MS Visual C++, namely MS Visual Studio .NET 2003, none of the screen shots and most of the pull down setting don't make too much sense.

Is there an up-to-date tutorial around?

If not, what kind of "new project" do I create? "Win32 Dynamic Link Library" does not exist on .NET 03. See page 2-14 to witness my confusion. I used MFC DLL and received build errors.

Thanks,
Jon
0 Kudos
Message 1 of 3
(3,076 Views)
Jon,

There is a knowledge base that discusses this issue. Really all you have todo is create a class library project then bring them in using .NET VIs. The knowledge base contains the general steps for everything you should need. Let me know if there is more I can do!

Knowledge Base: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/800e019836cdf9fe86256f17006c2e0b?OpenDocument

Have a great day!!

Allan S.
Applications Engineering
National Instruments
0 Kudos
Message 2 of 3
(3,075 Views)
"jboehm" wrote in message
news:506500000008000000B2F50000-1079395200000@exchange.ni.com...
> If not, what kind of "new project" do I create? "Win32 Dynamic Link
> Library" does not exist on .NET 03. See page 2-14 to witness my
> confusion. I used MFC DLL and received build errors.

I've got VC++ 2005 beta in front of me which is very similar. You just want
to make a new project, Win32, and in mine is says "Console Application
(Win32)". Under the project properties you can decide if you want to
generate a *.exe or a *.dll output.

The MFC DLL is going to import a bunch of graphical features that you
probably didn't intend to select. I usually just choose to make an empty
project and start coding. Make sure to define the functions to export (.d
ef
file or declexport) and then you can make your Call Library Nodes and use
them from Labview.

The alternative is to compile a .NET class or an ActiveX component. These
will "advertise" their methods and datatypes to Labview so you dont have to
sit around making Call Library Nodes all day.

Good luck!

-joey
0 Kudos
Message 3 of 3
(3,075 Views)