Vista - NetNamedPipeBinding Construction Causing Program Termination

Hi, all.

I'm getting some weird behavior when newing a NetNamedPipeBinding
object. In one version of my program, everything works fine. In
another, where execution takes a different path (static methods and
instances involved), the program just stops. I'm debugging in VS.NET
2005, and when I single-step past

NetNamedPipeBinding binding = new NetNamedPipeBinding(); ,

the IDE just stops debugging, no complaining involved. I've tried
having the statement in a try block and without, but I get the same
results: program termination.

Any ideas what might cause the IDE to do that? FWIW, the program is a
console app and the terminating statement is in a referenced assembly.

Thanks!
~swooz

The best thing I've ever figured out is something like this:

<system.diagnostics>
<trace autoflush="true" />
<sources>
<source name="System.ServiceModel"
switchValue="Information, ActivityTracing"<listeners>
<add name="sdt"
type="System.Diagnostics.XmlWriterTraceListener"
initializeData= "c:\wutemp\Client1.svclog" />
</listeners>
</source>
</sources>
</system.diagnostics>



and

SvcTraceViewer.exe - Learn It, Know it, Love It

http://wcf.netfx3.com/blogs/wcf_comm...t-love-it.aspx

I debugged a NamedPipe issue this way as well.

the above will at least give you the stuff to google and figure out.

you see the exact exceptions on the service side with these things.

You can also do this:



<system.diagnostics configSource="SystemDiagnostics.config">
</system.diagnostics>

so you have have different deploy strategies ... as in.. you don't want this
stuff on in production (as the normal behavior), but you can easily turn it
on in production if you need to.




"Swoozie Pellegrino" <swooziep@xxxxxx> wrote in message
news:1192570369.006119.42270@xxxxxx

Have you tried chnaging the bindings ? My gut feeling is with TCP or HTTP
binding you may not have this issue. This could be an internal thread issue
when using pipes.

"Swoozie Pellegrino" wrote: