Re: Development in IIS or on file system

Interesting points. Thanks for the details. Assuming that our developers
are all admins on our boxes, and that we all have IIS installed locally on
our machines, is there any good reason not to develop our applications right
in our local IIS instances?

Thanks again.

Mark

"Jim Cheshire" <nomail@xxxxxxxxxx> wrote in message
news:ri32t1pgc4fbui005rt08e3j384e30jl1b@xxxxxxxxxx
> On Fri, 20 Jan 2006 08:26:08 -0600, "Mark" <mark@xxxxxxxxxxxxxx>
> wrote:
>
>>Yes - testing is certainly done beyond development. However, it is my
>>responsibility to test my software thoroughly prior to handing it to the
>>tester. I can copy the files from the file system to my local IIS to test
>>... but again I lose the debug capabilities, not to mention the ease of
>>finding problems just by working natively in IIS all the time.
>>
>>Also - no loaded question was intended. Microsoft has created a "safe"
>>place for us to develop code, but it strikes me as a limited environment.
>>I'd love feedback on how others intend to balance the need for feeling
>>safe,
>>and the desire for increased functionality. Once we have our team head
>>down
>>one path, it would be a pain to change it for everyone.
>>
>
> Yes, the ASP.NET Development Server is a limited environment for sure.
> There are several reasons why we chose to go that route, but one of
> the most important ones is that it allows developers to run and debug
> code as non-administrators. This has traditionally been a painful
> process, especially for educational institutions and government
> agencies.
>
> One thing that you may not have thought of is using the ASP.NET
> Development Server to debug content that physically exists on an IIS
> instance. In other words, say that you have a Web server called Web01.
> You can map a drive (say the G drive) on your development box that
> maps to the content of your Web site on the Web server. In VS 2005,
> you simply open your project using that file path. Then when you
> debug, you will actually run against the ASP.NET Development Server,
> but you can also browse the exact same content on the IIS instance.
>
>
> Jim Cheshire
> --
> Blog:
> http://blogs.msdn.com/jamesche


.

Relevant Pages

  • Re: Remote Debbuging Problems...
    ... I have the asp.net project on the development server and I installed VS.NET ... If I debug the application and am running it from localhost it works fine. ... Once I got IIS down I could delete the files ... >I also am experiencing remote debugging problems. ...
    (microsoft.public.vsnet.debugging)
  • Re: Unable to debug
    ... I installed the VS2005 and the IIS on the same machine. ... the web server. ... It turns out you need to patch visual studio AND run it as the admin user, under vista, in order to be able to debug ASP.NET apps. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: VS 2003 cant debug on iis, Windows XP SP2,
    ... > Can not activate debug on web server. ... > IIS Lockdown 2.1, ... > displayed and hence can not enable both debugging option ...
    (microsoft.public.vsnet.general)
  • RE: VS 2003 cant debug on iis, Windows XP SP2,while executing VS proj
    ... > while executing VS project. ... > Can not activate debug on web server. ... > IIS Lockdown 2.1, ...
    (microsoft.public.vsnet.general)
  • Re: Unable to debug
    ... I installed the VS2005 and the IIS on the same machine. ... debug it. ... "Unable to start debugging on ... the web server. ...
    (microsoft.public.dotnet.framework.aspnet)