NetMessageBufferSend question

[Tom Wright]

I'm having trouble with the LPBYTE param of this API. I want to move text from my dialog based application to this api to send. LPTSTR buffer; m_cSendText.GetWindowText(buffer, 256); nasStatus = NetMessageBufferSend(NULL, awcToNameW, awcFromNameW, (LPBYTE)buffer, 256); When I run my program all I get is a string of ?'s. How do I setup the 4th param so that it sends the text properly? Thanks Tom Wright tawright915@yahoo.com

[Tom Wright]

Okay I found that I did not have this set correctly is should be CString buffer; m_cSendText.GetWindowText(buffer); nasStatus = NetMessageBufferSend(NULL, awcToNameW, awcFromNameW, (LPBYTE)&buffer, m_cSendText.GetWindowTextLength()); But I'm still getting junk in the message box. Any suggestions? Tom Wright tawright915@yahoo.com

[Stephen C Steel]

The problem is the unecessary & to take the address of the CString object. If you only need read access to the string data in a CString object, you can use the (LPCTSTR) conversion operator to get a pointer to the buffer. Then you'll have to use a cast, because NetMessageBufferSend() expects an LPBYTE rather than an LPCTSTR. That is, change (LPBYTE)&buffer, to (LPBYTE)(LPCTSTR) buffer, Casting away the constness of the LPCTSTR doesn't matter in this case, since NetMessageBufferSend () is only going to read the buffer. Stephen C. Steel Kerr Vayne Systems Ltd.

[Tom Wright]

No this still does not work. I must not be setting something up right. I have a dialog based app with 2 edit fields on it. And a control variables called: m_cCompName. m_cSendText. LPWSTR awcToNameW; LPWSTR awcFromNameW; CString ComputerName; awcToNameW = T2W(ComputerName); awcFromNameW = T2W(ComputerName); NET_API_STATUS nasStatus; nasStatus = NetMessageBufferSend(NULL, awcToNameW, awcFromNameW, (LPBYTE)(LPCTSTR)TextSend, TextSend.GetLength()); So what am I doing wrong. This should work. Right? Thanks Tom Wright tawright915@yahoo.com

[Daniel Lohmann]

Usually NetXXX Api never use ANIS strings. Even if not explicitly mentioned in MSDN, I would try to convert the message buffer also to UNICODE. -- Daniel Lohmann http://www.losoft.de (Hey, this page is worth looking! You can find some free and handy NT tools there :-D )

[Tom Wright]

That's what I ended up doing. Thanks Tom Wright tawright915@yahoo.com