John Lokanis Posted January 12, 2010 Author Report Share Posted January 12, 2010 What about using WriteFile instead of WriteConsoleA? That might make the redirection work. Nope. Back to the drawing board... Link to comment
Popular Post smenjoulet Posted January 13, 2010 Popular Post Report Share Posted January 13, 2010 Nope. Back to the drawing board... OK, I got piping/redirection to work. The key was some code/info posted on this C# thread. There are a couple more kernel32 dll calls now, so it's even farther from pure .NET. However, it works pretty good, both from console and System Exec. Next up: Develop similar method to allow a LabVIEW program to accept input from StdIn. -Scott Write Std Out with Redirection.vi 4 Link to comment
John Lokanis Posted January 13, 2010 Author Report Share Posted January 13, 2010 OK, I got piping/redirection to work. Sweet! This works for me. Only caveat is I cannot call it from the command line using start /wait to force it to wait until completion. However, calling it with "cmd /c myapp.exe" does work, will wait and redirection works too. Thanks! now to try this in my real world application and see if Python likes it! Link to comment
John Lokanis Posted January 14, 2010 Author Report Share Posted January 14, 2010 now to try this in my real world application and see if Python likes it! Confirmed! This solution works in all my test cases for my Console app! Thanks to smenjoulet! I owe you a beer at the next NI Week! Link to comment
faiob Posted March 6, 2012 Report Share Posted March 6, 2012 Please, can you save Write Std Out with Redirection.vi for Labview 8.2? Link to comment
asbo Posted March 6, 2012 Report Share Posted March 6, 2012 Write Std Out with Redirection.LV8.0.vi Link to comment
Rob Calhoun Posted November 21, 2017 Report Share Posted November 21, 2017 cross-reference: 32/64-bit compatible version of stdout writer for LabVIEW 2017. https://lavag.org/topic/20360-collecting-stdout-from-labview-when-run-from-jenkins/ Link to comment
hooovahh Posted December 11, 2017 Report Share Posted December 11, 2017 Do you know what a non-disclosure agreement is? Well you agree to one when you sign up for a LabVIEW beta, and you can be subject to whatever NI feels that are legally allowed to come after individuals for. One such restriction is to not discuss beta topics outside of approved areas. This can have a real negative impact on NI's business. LAVA is about minimal censorship and unless you, or NI complain I won't be editing your post, but if I were you I'd edit your post, or ask them to be edited. Link to comment
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now