By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,930 Members | 633 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,930 IT Pros & Developers. It's quick & easy.

ASP.NET Hosting Gotchas?

P: n/a
The other day in this group someone wrote that one of the ASP.NET hosting
providers is "...not an enterprise server, so for example you can't cache
web pages..."

I'm wondering what "not an enterprise server" means, and what the
ramifications are - other than an inability to cache web pages. More
importantly, I'm wondering what other limitations on ASP.NET are enforced by
the providers - and how I can discover what those limitations are. I'd like
to think that I just sign up and get access to all features of the entire
..NET Framework. I'd hate to develop production-ready applications, only to
have them choke because the hosting provider disallows caching or some other
basic feature.

I'd appreciate any guidance on avoiding ASP.NET hosting limitations - what
to look for, etc..
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
There are literally thousands of ASP.NET hosts out there and they
(unfortunately) don't all list their packages in a way that you can easily
compare with another host.

The best thing to do is to read the specs. on the service and email them
with questions (like this one) before you sign up.
"David Krussow" <sc******@schmuks-r-us.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
The other day in this group someone wrote that one of the ASP.NET hosting
providers is "...not an enterprise server, so for example you can't cache
web pages..."

I'm wondering what "not an enterprise server" means, and what the
ramifications are - other than an inability to cache web pages. More
importantly, I'm wondering what other limitations on ASP.NET are enforced by the providers - and how I can discover what those limitations are. I'd like to think that I just sign up and get access to all features of the entire
.NET Framework. I'd hate to develop production-ready applications, only to
have them choke because the hosting provider disallows caching or some other basic feature.

I'd appreciate any guidance on avoiding ASP.NET hosting limitations - what
to look for, etc..

Nov 18 '05 #2

P: n/a
PJ
check out www.webhost4life.com . very reasonable prices and xlnt customer
services. if you do use them, please put my username in a referral:
"pjwal". ;-)
"David Krussow" <sc******@schmuks-r-us.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
The other day in this group someone wrote that one of the ASP.NET hosting
providers is "...not an enterprise server, so for example you can't cache
web pages..."

I'm wondering what "not an enterprise server" means, and what the
ramifications are - other than an inability to cache web pages. More
importantly, I'm wondering what other limitations on ASP.NET are enforced by the providers - and how I can discover what those limitations are. I'd like to think that I just sign up and get access to all features of the entire
.NET Framework. I'd hate to develop production-ready applications, only to
have them choke because the hosting provider disallows caching or some other basic feature.

I'd appreciate any guidance on avoiding ASP.NET hosting limitations - what
to look for, etc..

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.