just my thought process...!

Here I would like to share some information on how to debug a remote process running on a different machine. For example take below scenario: 1. We don’t have VS.Net framework installed on a machine/vm, let’s say machine–1. 2. We have VS.Net installed on your production machine. Let us say machine- 2. 3. Able to access machine -1 from machine-2. 4. We have to attach and debug a remote ‘.exe’ process running on machine-1 then, copy “Debugger” folder [C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages ] from machine-2 to machine-1. Open command prompt and go to ‘Debugger’ folder on machine-1 and run below command msvcmon -tcpip -timeout -1 -anyuser machine-1 will now be in listening mode for connections. Now, go to machine-2. Launch VS.net and choose ‘Debug Process’ from ‘Tools’ menu. Choose, ‘TCP/IP’ from ‘Transport’ drop down list. And mention the ‘hostname’ or ‘IP Address’ of machine-1 in the ‘Name’ f

Recently when talking with a friend, our discussion turned towards motivating people. We were discussing the efforts put in our work but see failures, get ourselves stressed out and feel dissappointed. I shared with him this good old secret which my father told me when I was disappointed with my results. He said everybody in this world will be passing through their success cycle and failure cycle. We would get successful results in whatever we do when we are in success cycle. It always doesn’t mean that we are putting rite efforts. Sometimes even when we do things wrong those would yield/lead us to success. And the failure cycle, it’s vice versa. Nothing would work out when we are in this cycle. Does that mean we aren’t putting our efforts? Certainly, no I wondered when I started understanding this. You may now be having below BIG questions pondering in your mind. a. How can we find in which cycle are we now? b. Is there any fixed time span for these cycles? c. And what to do when I fi