Infralution Support

[DaveB]

One of my programmers is reporting that a socket read is returning immediately with no data when he runs the encrypted version of our app (even though there has been data written to the socket from another application).

We are using .Net 3.5, and he is using TCPClient and TCPListener for managing socket traffic. I have not had a chance to troubleshoot this myself, but before I do I want to know if there are known issues in this area?

The socket read works fine when using the non-encrypted version of the app.
Thanks,
Dave
_________________
Dave

[DaveB]

After speaking further with the programmer, it seems that the encrypted app is doing the socket write, and it's the other app that is reading zero bytes from the socket.

So, he is guessing that the encrypted version of our app is somehow failing to write the bytes to socket.

Any ideas?
_________________
Dave

[Infralution]

There are no known issues with using sockets. I think it is unlikely that the encryption is causing this problem - but anything is possible. You should be able to build a debug version of your bootstrapper and debug the problem to see exactly what is occurring.

If you can manage to isolate the problem in a small test project would be happy to look at it.
_________________
Infralution Support

[DaveB]

You were right, it had nothing to do with sockets.
Here is the offending code:

Assembly assembly = Assembly.GetExecutingAssembly();
DateTime buildDate = File.GetCreationTime(assembly.Location);

...assembly.Location is an empty string when we run the deployed (encrypted) version of the app, and GetCreationTime throws an exception.
_________________
Dave

[Infralution]

Since the encrypted assemblies are dynamically loaded they don't actually have a location - so you have to be careful about calls to assembly.Location. You could possibly replace this with: