Hello,
The company is on the .Net solutions push company wide which will be implemented sometime in the near future. Of course, one of the big concerns is IIS running on a developer's workstation. The one thing I have heard is using the IIS Lockdown Tool to secure the developer's workstation, which I have used in doing some .Net Training here at home. The Lockdown Tool stopped any development work I was doing with ASP.NET and IIS and I had to unlock IIS to continue development work.
The person who is basically a Training person is involved with the decision making process with Systems and Tech Support, which I started talking with about using IIS and .Net from a developer's standpoint.
It's just like with InterDev that was installed on my machine. I cannot fully use InterDev to debug and ASP application from my workstation, because IIS is not on the workstation and one must go through some Mickey Mouse routine by debugging an ASP application on the DEV Web server using response.write and other means, instead of being able to use the debugging tools in InterDev.
Like the Training person indicated they are concerned about FTP services and shutting it down or a contractor coming in and hacking IIS on a developer's machine. There is also laptop workstations that leave the building using VPN work situation etc., etc, which PFW for dial-up users or NAT router is used supplied by the company.
I would like to get a little feed back from the NG concerning the security issues and possible solutions and/or workarounds. As I would like to avoid the situation the developers face with using InterDev when ..Net is deployed to the developer's workstation and it cannot be used to its fullest capabilities as a development tool.
Thanks
Duane :)