G
Guest
When will Microsoft make it easier for web hosts / web hotels to support
COMPILED ASP.NET code? As far as I know, very few supports this because of
security or administrative issues. This is probably the main reason that
keeps ASP.NET from becoming more popular than PHP. (Which is NOT a goal in
itself, no flamewar thanks!)
First, as far as I know, web hosts can already "lock" code into the bin
directory with no possible way of reading or writing anywhere outside this
space. However, I don't know what support there is to stop bad code running
amok, taking up too much cpu. If there already is a solution to this, why are
most web hosts still not allowing compiled code because of "security issues"?
Second, there must be an easier way of creating more web applications. Most
of those few web hosts who allow compiled code still don't allow more than
one web application (Brinkster is one example). This means cramping all the
code into ONE bin directory, only having ONE web.config etc, which makes
installation of many applications a real pain if not totally impossible. (For
example, installing the ASP.NET Community Forums anywhere outside the webroot
without a separate webapplication requires heavy search-and-replace recoding.
And here we're lucky because we have the code, which might not always be the
case).
Obviously, some things need to be improved for web hosts to embrace compiled
ASP.NET fully. I really do hope Microsoft is taking this matter seriously.
COMPILED ASP.NET code? As far as I know, very few supports this because of
security or administrative issues. This is probably the main reason that
keeps ASP.NET from becoming more popular than PHP. (Which is NOT a goal in
itself, no flamewar thanks!)
First, as far as I know, web hosts can already "lock" code into the bin
directory with no possible way of reading or writing anywhere outside this
space. However, I don't know what support there is to stop bad code running
amok, taking up too much cpu. If there already is a solution to this, why are
most web hosts still not allowing compiled code because of "security issues"?
Second, there must be an easier way of creating more web applications. Most
of those few web hosts who allow compiled code still don't allow more than
one web application (Brinkster is one example). This means cramping all the
code into ONE bin directory, only having ONE web.config etc, which makes
installation of many applications a real pain if not totally impossible. (For
example, installing the ASP.NET Community Forums anywhere outside the webroot
without a separate webapplication requires heavy search-and-replace recoding.
And here we're lucky because we have the code, which might not always be the
case).
Obviously, some things need to be improved for web hosts to embrace compiled
ASP.NET fully. I really do hope Microsoft is taking this matter seriously.