# Debugging nameko services with Visual Studio Code

**URL:** <https://discourse.nameko.io/t/debugging-nameko-services-with-visual-studio-code/238>\
**Category:** googlegroup\
**Created:** [February 13, 2018, 2:06pm UTC](https://discourse.nameko.io/t/debugging-nameko-services-with-visual-studio-code/238 "2018-02-13T14:06:44Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mattbennett](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/mattbennett/32/13_2.png) [@mattbennett](https://discourse.nameko.io/u/mattbennett)\
**Post date:** [February 18, 2018, 8:29pm UTC](https://discourse.nameko.io/t/debugging-nameko-services-with-visual-studio-code/238/4 "2018-02-18T20:29:05Z")

</div>

Chris, do you also run Nameko on Windows? I've never actually tried it  
before... does it work?

> **···**
>
> On Sunday, February 18, 2018 at 6:07:33 PM UTC, Chris Platts wrote:
> 
> > Thanks, Tuan -- I'll give that another try!
> > 
> > I was pretty sure I'd tried the above, but hit a problem with vscode  
> > complaining about something being binary when it wasn't expected. Perhaps  
> > this is to do with debugging on Windows, where the 'nameko` command is a  
> > binary executable rather than a script shebang'd to point to python.exe.
> > 
> > (I'm trying to hit that perfect vscode configuration where I can hit F5 on  
> > a service.py and it'll run under the nameko shell on Windows, Linux and  
> > macOS).

---

_[View the full topic](https://discourse.nameko.io/t/debugging-nameko-services-with-visual-studio-code/238)._