Re: Developing ASP.NET w/out IIS or Admin Rights
- From: "GroupReader" <newsgroups_01@xxxxxxxxxxx>
- Date: 10 Oct 2006 10:50:35 -0700
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.
.
- Prev by Date: Re: Searching Content
- Next by Date: Re: Shopping Cart recommendations
- Previous by thread: Re: Developing ASP.NET w/out IIS or Admin Rights
- Next by thread: Re: Developing ASP.NET w/out IIS or Admin Rights
- Index(es):
Relevant Pages
|
