All Answers

All Answers » Re: Testing remote connection while in dev. environment » Comments for "Re: Testing remote connection while in dev. environment"
  • Darren
    Hi Luca, It does (normally) if you use Conveyor as I posted above. Conveyor is designed allow remote connections to a dev. environment. I don’t have the tools to hand, but I’m quite positive I’ve connected remotely at home from my Android phone to a wisej app on my laptop – over WiFi. The same isn’t working on my company lan, however – hence this post.
  • Luca (ITG)
    Conveyor is a tunneling app. It simply makes external connections become local (127.0.0.1), which can cause other issues. Using IIS (not IIS Express) with VS in debug mode is quite normal and works very well.
  • Darren
    Hi Luca, If you’re saying that Conveyor, Wisej & IIS Exp. aren’t well suited, what is the best method to test multiple client connections to a web app. whilst developing? (Sorry, it’s still all new to me) Thanks
  • Darren
    Actually, if I select “Use Visual Studio Dev. Server” – the app. no longer works (I don’t even see the loader animation). So only “Use IIS Express” is working for me!
  • Luca (ITG)
    It’s not related to Wisej. Conveyor tunnels the connection that’s why you get 127.0.0.1 as the remote address and need to use the forward-for header. Once you deploy chances are that x-forwarded-for is null.
  • Luca (ITG)
    I don’t see the “Use Visual Studio Dev Server” option. I was referring to “Use IIS”. See https://docs.microsoft.com/en-us/visualstudio/debugger/how-to-enable-debugging-for-aspnet-applications.