Web Development on Terminal Server

[Matt_B]

We are looking to move to Terminals at work, I wondered if any .net developers on here have any experience on this? In particular can I still locally debug, i.e. ctrl+F5 to get localhost:5995 or whatever port, or will I have to attach to the processes etc?

 

[Mike - True Blue Tinter]

We are looking to move to Terminals at work, I wondered if any .net developers on here have any experience on this? In particular can I still locally debug, i.e. ctrl+F5 to get localhost:5995 or whatever port, or will I have to attach to the processes etc?

I am sorry, but you need to get out more!

Is the Big Bang Theory your favourite TV programme? :icon_lol:

 

[Macky]

We are looking to move to Terminals at work, I wondered if any .net developers on here have any experience on this? In particular can I still locally debug, i.e. ctrl+F5 to get localhost:5995 or whatever port, or will I have to attach to the processes etc?

Sorry Matt, can't help, not something I've any experience of. I wouldn't have thought it would be any where near as straightforward as working locally though.
What's the thinking behind the move? Multiple developers on a project?

I am sorry, but you need to get out more!

:icon_conf It's work, not a hobby.

 

[Matt_B]

Sorry Matt, can't help, not something I've any experience of. I wouldn't have thought it would be any where near as straightforward as working locally though.
What's the thinking behind the move? Multiple developers on a project?




:icon_conf It's work, not a hobby.

Unfortunately it is cost. We all work locally at the minute and deploy to dev and testing servers at the appropriate stages, it works very well. The problem is we now have a new MD, who uses terminals in his other company (where there are only a few developers working on their own stuff) and he thinks it will be cheaper on licenses for us to do it.

We might also go down to single, though larger, monitors, which will kill me.