Hello all,
I'm new to .NET but have experience in Visual Basic 6.0
I have recently written an application in VB.NET 2008 Express which uses a reference to the old mswinsck.ocx instead of the new sockets stuff. The application works great on the machine it was developed on, however when I attempt to install it on any other computer (used the Publish feature) it always crashes and gives a message box asking the user to send an error log to Microsoft.
The application also generates two log files (one for logging data from the sockets connection and the other for debugging purposes). When the app has been deployed neither log file gets generated so I can't even determine how far it gets or where it dies!
Questions:
1. Has anyone seen this before and how did you solve it?
2. Where is the local application path on the deployed machine? (i.e. where would my log files be generated?)
Thanks,
vbahuse
I'm new to .NET but have experience in Visual Basic 6.0
I have recently written an application in VB.NET 2008 Express which uses a reference to the old mswinsck.ocx instead of the new sockets stuff. The application works great on the machine it was developed on, however when I attempt to install it on any other computer (used the Publish feature) it always crashes and gives a message box asking the user to send an error log to Microsoft.
The application also generates two log files (one for logging data from the sockets connection and the other for debugging purposes). When the app has been deployed neither log file gets generated so I can't even determine how far it gets or where it dies!
Questions:
1. Has anyone seen this before and how did you solve it?
2. Where is the local application path on the deployed machine? (i.e. where would my log files be generated?)
Thanks,
vbahuse