What does you code do ?

@bitlixi's advice worked for me

yes it does

I am exactly getting the same problem may be we need to add exception in MSVC

Thanks for the reply. I have read the link about the pipe and tried a couple of other things (they didnt' work anyway )

First, i renamed the external pipe in VmWare settings to : superpipe22. I made sure, that the pipe is connected to vmware. Also the name of the computer in VmWare operating system (windows 8) is : SUPERPC
Then i changed the server creation first like this:
**
cdb -server npipe:pipe=\S
UPERPC\pipe\superpipe22 C:\tests\clean_deploy\clean_deploy\myapp.exe**

and tried to connect with
npipe:server=SUPERPC,pipe=\SUPERPC\pipe\superpipe22

npipe:pipe=\SUPERPC\pipe\superpipe22

npipe:server=SUPERPC,pipe=superpipe22

npipe:server=SUPERPC,pipe=superpipe22

Then i went to cdb folder, manually ran it and tried:

1

cdb -QR \\SUPERPC
Servers on \\SUPERPC:
Unable to query \\SUPERPC

2

cdb -QR \\SUPERPC\pipe\superpipe22
Servers on \\SUPERPC\pipe\superpipe22:
Unable to query \\SUPERPC\pipe\superpipe22

3

cdb -QR \\.\pipe\superpipe22
Servers on \\.\pipe\superpipe22:
Unable to query \\.\pipe\superpipe22

So cdb cannot access the VmWare even trough the pipe. I think the problem is that VmWare is not reachable under the name SUPERPC. I know its not the topic of this forum, but can you suggest any tips, on how i can access my VmWare OS by the servername? My VmWare is not using bridged connection it has its own network with its own modem etc. (That's why i'm testing my application there).

Well, if you've been using it already for so long and you didn't find it frustrating then it's okay, my comment was only for newbies (and you're no longer in that category after months of using it)