ASP.NET 2.0 installs web projects by default in the file system, leveraging
the increased security of the new personal web server, rather than relying
on hacker prone IIS. However, it strikes me that this will add more
headaches for testing because your development doesn't use IIS. For
example, you lack the benefits of testing withing the VS IDE with debugging,
as well as identifying IIS issues upfront. We work in an environment where
Microsoft's updates are automatically downloaded and installed, keeping IIS
ideally as up to date as Microsoft is able to make it.
Aside from the obvious security benefit of not using IIS, are there other
advantages/disadvantages/work arounds that should be considered here?
Thanks in advance.
Mark 6 1410
On Fri, 20 Jan 2006 07:55:53 -0600, "Mark" <ma**@nojunkmail.com>
wrote: ASP.NET 2.0 installs web projects by default in the file system, leveraging the increased security of the new personal web server, rather than relying on hacker prone IIS. However, it strikes me that this will add more headaches for testing because your development doesn't use IIS. For example, you lack the benefits of testing withing the VS IDE with debugging, as well as identifying IIS issues upfront. We work in an environment where Microsoft's updates are automatically downloaded and installed, keeping IIS ideally as up to date as Microsoft is able to make it.
Aside from the obvious security benefit of not using IIS, are there other advantages/disadvantages/work arounds that should be considered here?
At the risk of answering what appears to be, at least in part, a
loaded question, it's important to remember that development and test
are two different stages.
Jim Cheshire
--
Blog: http://blogs.msdn.com/jamesche
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.
Thanks again.
Mark
"Jim Cheshire" <no****@nomail.com> wrote in message
news:gg********************************@4ax.com... On Fri, 20 Jan 2006 07:55:53 -0600, "Mark" <ma**@nojunkmail.com> wrote:
ASP.NET 2.0 installs web projects by default in the file system, leveraging the increased security of the new personal web server, rather than relying on hacker prone IIS. However, it strikes me that this will add more headaches for testing because your development doesn't use IIS. For example, you lack the benefits of testing withing the VS IDE with debugging, as well as identifying IIS issues upfront. We work in an environment where Microsoft's updates are automatically downloaded and installed, keeping IIS ideally as up to date as Microsoft is able to make it.
Aside from the obvious security benefit of not using IIS, are there other advantages/disadvantages/work arounds that should be considered here?
At the risk of answering what appears to be, at least in part, a loaded question, it's important to remember that development and test are two different stages.
Jim Cheshire -- Blog: http://blogs.msdn.com/jamesche
On Fri, 20 Jan 2006 08:26:08 -0600, "Mark" <ma**@nojunkmail.com>
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
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" <no****@nomail.com> wrote in message
news:ri********************************@4ax.com... On Fri, 20 Jan 2006 08:26:08 -0600, "Mark" <ma**@nojunkmail.com> 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
On Fri, 20 Jan 2006 13:15:55 -0600, "Mark" <ma**@nojunkmail.com>
wrote: 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?
No, in your scenario, you can certainly use the local IIS instance.
Jim Cheshire
--
Blog: http://blogs.msdn.com/jamesche
Mark,
To add to Jim's answer, at my main job (F+W Publications, Inc.) we develop
on IIS and I develop using IIS for my own side business also. I prefer it
that way for many of the same reasons you are thinking of doing it. And my
setup is similar to yours in many ways. I would recommend doing one thing if
you're worried about IIS possibly being compromised. Because we have our
development boxes opened up at work (not to the public but internally) we
run software firewalls and allow only local 127.0.0.1 access to IIS. That
locks it down pretty tightly.
Regards,
--
S. Justin Gengo
Web Developer / Programmer
Free code library: http://www.aboutfortunate.com
"Out of chaos comes order."
Nietzsche
"Mark" <ma**@nojunkmail.com> wrote in message
news:ez**************@TK2MSFTNGP09.phx.gbl... 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" <no****@nomail.com> wrote in message news:ri********************************@4ax.com... On Fri, 20 Jan 2006 08:26:08 -0600, "Mark" <ma**@nojunkmail.com> 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
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Me |
last post by:
I would like to redesign my existing site into php using classes.
I am not the most experienced developer with PHP, and would like to know
if anyone can give me some input on a starting point for a...
|
by: KingIshu |
last post by:
Hi All,
I am developing an object oriented OS code-named "ikbocs".
1) What are the pros and cons of the following languages interms of
Effectiveness on System Programming, Object Orientedness etc...
|
by: Alex |
last post by:
Hi all,
I am trying to install a java stored procedure via the windows
development centre.
The linux box is running 8.1 FP4 as is the windoze platform. If I am
on the linux box i can install...
|
by: Pascal Frey |
last post by:
Hi,
I just wrote a small simple C# application with a small gui. I was testing
the application continous on my development system. Now i tried to let it
run on another system but it doesn't.
On...
|
by: Klaus Jensen |
last post by:
Hi!
I have a pretty traditional setup where I develop on my local PC and the use
"Copy Project" to deploy to the production enviroment.. In web.config I need
different values for...
|
by: Mark |
last post by:
The new file based web server that comes with Visual Studio 2005 allows you
to develop and debug an ASP.NET on a remote computer rather than having to
rely on IIS. Assuming you've got decent LAN...
|
by: Richard Levasseur |
last post by:
(Forewarning, most of these problems and solutions come from being the
only developer in a 1 server department with no budget, few resources,
unresponsive IT, and non-technical managers, so thats...
|
by: situ |
last post by:
Hello all,
i have Database1 and database2,
is it possible to make database connection to database2 by running
stored procedure on database1.
Thanks and Regards
Situ
|
by: macca |
last post by:
Hi,
I just started a new web developer job (my first actually) and the
machine they gave me to use is a Mac. Two days in and I'm running a
Win XP environment on my Mac at work (using VMWare), ...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
| |