>Mark,
>
>I develop on one system and deploy on another. My development system is either my NT Server with IIS at home, or a Win 98 running PWS at work.
>
>The home machine has a complete set of data files for test purposes, in the same directory structure as the live system.
>
>The work machine has a complete set of test data files, and can also be easily switched over to the live data on the same network.
>
>When a new EXE is ready to deploy on the live system, I just put the EXE in a certain directory and run Web Connection's Update EXE routine, which shuts down any running instances, copies in the EXE, and the site keeps on running...
>
>That's with Web Connection, running EXE servers thru ISAPI-style plumbing. If you're running under ASP's it may be a different story.
>
>This kind of technical issue is one of the reasons I so strongly encourage people to use WC. Rick has worked out many of the bumps in the road already.
>
>>My question guys is how do you develop Web apps?. Does everyone have to follow that procedure:
>>1.Kill EXE.
>>2.Kill InetInfo
>>3.Go to Control panel/Start Web Service (no need on W2000 starts automatically in ~ 30secs.)
>>4.Recompile EXE.
>>5.Run (sometimes I have to repeat steps 1-3)
>>6.More errors to fix.
>>7.Repeat all the steps.
>>Or I am wrong?
>>Thanks Mark
I am talking about development machine with NT. Just like right now I closed browser on my laptop I use to test apps. Started it again and it does not work. I have to go over NT, kill EXE, InetInfo (almost every time) and blah, blah.....
Try to test again.
Mark