VB6 COM+ to .NET interop

Question

1.00/5 (1 vote)

See more:

Recently, we have implemented change to integrate COM+ application with a .Net class library (to consume IBM ESB services).

.Net class library is reading the output string from web service and passing this string to VB as reference parameter.

Issue, when the output string data has '\r'(carriage return char OD) then .Net is trying to convert to ASCII but not able to and this passing the value as '?' to VB. VB is failing because of the '?'3F  char.

Is there is any way in which .Net should not try to convert the string .

What I have tried:

• Tried to pass the output string as base64 char

• Tried to pass the output string as character array

Posted 21-Dec-17 17:50pm

Member 13032309

Updated 26-Dec-17 22:06pm

v2

Add a Solution

Comments

Richard MacCutchan 22-Dec-17 4:08am

0x0D is carriage return ('\r'), not newline.

Member 13032309 27-Dec-17 4:05am

Hello Richard,

'\r' (OD) is coming from Mainframe and VB is throwing parser error. Any idea idea on this issue ?

Richard MacCutchan 27-Dec-17 4:20am

I have no idea what the mainframe is doing, or what .NET class library you are using, or how you have written your VB code. But the obvious suggestions are to get the mainframe to send a proper newline character. Or change the code in the class library, or VB to recognise what you are receiving.

Member 13032309 3-Jan-18 19:13pm

Hi Richard,

It was working before when C++ was reading the data from mainframe and providing the same string to VB. But now, after adding .Net class library issue is occurring. Is there any way to remove this char in .Net Class Library ?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)