How to build a CIN code resource (.lsb file) and VC++

[Raymond Mouthaan]

Hello Anyone,

I did exacly the tutorial "How to build a CIN code resource (.lsb file)" at
http://zone.ni.com/devzone/conceptd.nsf/webmain/31DAB548C369B2C6862567C8006D
8FC9?opendocument#1 ,but I get this error in VC6.


--------------------Configuration: VI_Name - Win32 Debug--------------------
Linking...
Creating library Debug/VI_Name.lib and object Debug/VI_Name.exp
Performing Custom Build Step on .\Debug\VI_Name.dll
Error executing c:\windows\system32\cmd.exe.

VI_Name.dll - 1 error(s), 0 warning(s)
----------------------------------------------------------------------------
-----


The *.c file was compiled successfully and dll file was build, but the lsb
never shows up.

Does anyone know what this means? I
'm not sure if the problem relies on
LV6.1. A previous problem about this topic has been solved by the help of
Scott H. Thanks for that Scott and hopefully you have an explaination
for this one.

If you (anyone) don't know the answer to the problem, but you are able to
build a .lsb file, please send me a zip or rar file containing the Visual
C++ source code (workspace, *.c and so), the VI with CIN. It could be really
helpfull.


FYI, I have Windows XP as OS with Visual Studio 6 installed.

Thanks for your cooperation.

Regards,

Ray

[Enrique]

Raymond;

I wrote a small VI just to do the CIN custom step, because small mistakes in VC++ cause big headaches.

You can download this VI at: http://www.jyestudio.com/lview.shtml

I hope this work for you.

Regards;
Enrique

[Randy_H]

Ray,

Have you read the Using External Code in LabVIEW manual? It ships in the LabVIEW Bookshelf as a PDF and can also be found on our web site. It gives you a step by step, file by file method of creating a CIN in Visual Studio C++. I have never had any issues when I follow its description.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

[marc lawrence]

I had the same problem. The reason was due to 'copy and paste' from the PDF file.... It inserted a 'newline' charactor into the 'custom build' setup. The code appeared ok (wrapped) but it refused to work. Typing the code in by hand removed the 'wrapping' and solved the problem.

Marc