• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 198
  • Last Modified:

Running VS.NET on production server

I'm a web developer migrating from using Dreamweaver/ASP Classic to Visual Studio.net. The stability of Dreamweaver allowed me to feel secure installing Dreamweaver directly on the server so that I could make minor edits to pages even if I didn't have access to my developement workstation...just establish a Terminal Services connection (dialup speeds worked just fine) and run the app on the server.

VS is a different animal completely. Not to mention the fact that now I'm compiling programs instead of just editing text files. The question for you folks is - is it practical/advisable to install VS on the server (winServer2003) to accomplish the same 'off site' editing I'd had with Dreamweaver?

tx
--steve...
0
juststeve
Asked:
juststeve
  • 3
  • 3
1 Solution
 
softplusCommented:
Hi Steve,
If your permissions are set correctly this should not be a problem. Anyone who can access your VS.NET through the internet will also be able to download/install it if it wasn't there in the first place. Yes, you're going to have a big pile of software installed (maybe not use the standard location?), but if your webserver is locked down how it should be then you shouldn't have a problem. But as always, the more things available, the more things that can go wrong :).
John
0
 
juststeveAuthor Commented:
Thankx John...I just needed that re-assurance. I guess I tend to think of a 'server' as something fundamentally different than a workstation. Something almost Holy. I'm working to get over that.

--steve...
0
 
softplusCommented:
Thanks Steve :) - yep, that server is just a stupid pc with a bit box around it :)). I'd just make sure that everything is properly secured then it will be ok (+ VPN tunnel for the remote desktop and don't forget about installing regular patches for everything including VS.NET). I have VS.NET on one of my servers as well, for the reason you mentioned and to get more feedback if someone has problems using VS.NET remotely (helps determine if the cause is on the server or at the client).
John
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
juststeveAuthor Commented:
quick followup...I've just implemented VPN (i'm all of a month into the world of broadband, if you can believe that). How do I specify that Remote Desktop use the VPN vs. standard connection?
0
 
softplusCommented:
Uuuf, you're asking questions :). I did all of this on my firewall, i.e. only have ports 80/25/110 open for the server to the WAN. The VPN tunnel originates from my firewall and will allow me access to the other ports on the servers in the DMZ. If you don't have a firewall between the server and the web, I'd really, really, REALLY recommend getting one -- if you do, make sure it has separate ports for DMZ and best of all, one that can do VPN :). I have a Sonicwall Pro somethingorother, but there're lots out there now, I wouldn't know which one to recommend.
John
0
 
juststeveAuthor Commented:
Got it...umm...errr...got enough to pass on to my webhost anyway....thankx!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now