Domain Availability
Domain Whois
Ping Test
Reverse/IP Lookup
Server Status
Website Speed Test

Backlink Checker
PageRank Checker
PageRank Prediction
Link Popularity
Keyword Suggestion
Rank Checker
Multi-Rank Checker
Search Engine Position
Search Listings Preview
Spider View

HTML Optimizer
HTTP Headers
Link Extractor
Meta-Tags Extractor
Meta-Tags Generator
Source Code Viewer





Upgrading to ASP.Net 2? Why Your Website Might Stop Working When You Do.
By : John Belthoff

Asp.Net version 2 was just recently released by Microsoft and contains a feature rich set of classes that can do just about anything imaginable. However if you are thinking about hosting your 2 site on a shared hosting environment there are a few considerations you should know about before you take the plunge. If you have already upgraded you may be wondering why your site that was working fine in version 1.1 but now has problems working in Asp.Net version 2.

Code Access Security

If you receive one of those generic yellow error messages that say something like the following:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Net.WebPermission, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

The Reason? - Code Access Security!

As it turns out many shared hosting companies are setting the Security Trust level in the version 2.0 machine.config files to the default "Medium" setting then locking it down so it can't be overridden by the application.

This is great from hosting perspective but not so good if you are a developer that uses functions like xml.load from another website, webrequest, webclient,, etc... or many other classes that a default medium trust setting doesn't allow.

What can you do?

There are a number of considerations on how to rectify this situation and the first is to contact your hosting company and ask them to create a modified version of the medium trust machine.config file to allow for the features you want to implement.

Microsoft has provided an article that describes this process and if you're hosting company is not aware of it than shame on them.

The article can be found here: - How To: Use Medium Trust in ASP.NET 2.0

Give this a good read as it explains not only how to modify medium trust but also how to code for the medium trust settings.

If that is not an option you might want to consider recoding your entire website to conform to medium trust, not a very good option, or moving to a hosting company that will work with you for your particular needs.

Allowing open socket connections is a security risk for a hosting company, but if you can establish that your code is not malicious a reputable hosting company should provide you with proper security clearance to utilize the rich classes that version 2.0 has to offer. After all they are claiming to sell you version 2.0. And if you can't use version 2's classes than you are not getting what you paid for.

Over time there will need to be a balance between the hosting companies security needs and the ability of a web developer to utilize the classes that make version 2.0 so brilliant and I hope that time comes sooner rather than later.



About the Author :
About the Author: John Belthoff is a Professional Audio Engineer and an Avid Web Developer who plays and also teaches Jazz Guitar in his spare time. His latest web projects include the Internet Production Guide: and he owns a small Asp Hosting Company: You can contact him at his personal web site Studio JB:

Copyright 2006 - All Rights Reserved