Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1084392" data-attributes="member: 82144">Hello MichaelOff the top of my head, I think you'll find that SetupTv is checking whether the TV service is running by checking if the Windows service &quot;TVService&quot; is running. Normally that service looks for the TvService.exe in your TV Server install folder... but if you're debugging, you're probably running a TvService.exe from a build bin\Release or bin\Debug folder, and therefore the Windows service is not actually running. In other words its a case of different TvService exes that I think is causing the problem.For myself I never run the service or configuration out of build folders. I have scripts that clean and then copy the required files to my install directories. In other words, I do a sort of install/upgrade. To debug I insert a call to System.Diagnostics.Debugger.Launch(); which allows me to attach VS to the running process at the point I'm interested in... or I can use the general VS attach to process debug menu option to debug the service in its current state.Hope that helps...mm</blockquote>

[QUOTE="mm1352000, post: 1084392, member: 82144"] Hello Michael Off the top of my head, I think you'll find that SetupTv is checking whether the TV service is running by checking if the Windows service "TVService" is running. Normally that service looks for the TvService.exe in your TV Server install folder... but if you're debugging, you're probably running a TvService.exe from a build bin\Release or bin\Debug folder, and therefore the Windows service is not actually running. In other words its a case of different TvService exes that I think is causing the problem. For myself I never run the service or configuration out of build folders. I have scripts that clean and then copy the required files to my install directories. In other words, I do a sort of install/upgrade. To debug I insert a call to System.Diagnostics.Debugger.Launch(); which allows me to attach VS to the running process at the point I'm interested in... or I can use the general VS attach to process debug menu option to debug the service in its current state. Hope that helps... mm [/QUOTE]

Verification