1st, thanks for the reply. Working on a gov't contract has restrictions I
give you that --- it's very hard to convince the it security/network folks
about what software/services/ports you need to have running in order to
remain a productive developer ---- their philosophy --- "SECURITY OVER
CONVENIENCE".
On my team we are the architects, developers, DBMS admins, etc. so we can
install our applications on the remote server. We are also informed that ALL
web servers must have valid SSL certificates (443); which is being
interpreted as local versions of IIS for development purposes.
I'm not really concerned about the SQL set-up, as you've mentioned we can do
anything we need with the Enterprise Tools installed on our local machine to
access the server. I do not know the affects we will encounter by having our
web services shut down and IIS removed from our local machines.
Q: Is there a work around, while still stepping through code and debugging,
with 8 other people developing, maintaining, and testing other applications
off of the same IIS Server on the remote machine.
I know we will definately be "stepping" on each other when it comes to
stopping/restarting services or rebooting the server, but it looks like we
will not have a choice in this matter.
Thanks in advance.
We only have one version of VS.NET 2005; all developers currently have
VS.NET 2003.
"GroupReader" wrote:
I'm impressed that you kept your cool while asking that question.
Nothing ticks me off more than when a person is paid to develop
applications but isn't allowed to use the proper tools to do so.
Answer #1: You need access to IIS. Eventually you will need to
install the app on the server. You'll need access to do the
installation. At a minimum, you should have access to your local IIS
so that you can tell the administrator how to set up IIS on the web
server. Same goes for the database - how can you tell your DB Admin
what to do on the production box, if you aren't allowed to try it out
locally (or in a TEST environment) first??
Answer #2: Visual Studio 2005 solves much of this problem with the
"personal web server". You can run an ASP.Net app without IIS and
Visual Studio will launch it's own "personal" web server. This is an
okay solution for the bulk of development, but you'll still need to
refer to Answer #1 when it comes time to system test and install your
app. As for the DB, it's irritating, but not really that big of a deal
if you are not allowed to have a local SQL Server running. You'll
still have all the client tools installed, right? (Query Analyzer,
Enterprise Manager, etc...) Use this as an excuse for upgrading to
ASP.Net 2.0 and Visual Studio 2005.
