Our shared servers are configured to run ASP.NET applications as Medium trust level. This trust level prevents access to the registry and the Windows event log. In addition, your application is confined to files within a specific IP address range as well as within your application's virtual directory hierarchy. We have enabled database permissions however so that you can create applications that interact with a database.
Yes. Through the Customer Control panel you can select ASP.NET 2.0 for your website, or you can contact us and we will make the change for you.
No. Our servers have been upgraded to allow for both ASP.NET 1.x and ASP.NET 2.0. You can use either version at no additional charge.
If you are using Visual Studio, you can use the ASP.NET Development Server built into Visual Studio to test your pages. The server functions as a local Web server, running ASP.NET Web pages in a manner virtually identical to how they run on a Web server. Once testing is completed you can upload your pages to our servers.
Server-side code is processed on the server and is not sent to the browser, so users cannot see it. However, client script is not protected; any client script that you add to your page or that is injected into the page by server processing is visible to users. If you are concerned about protecting your source code on the server, you can precompile your site and deploy the compiled version.
You can write code for your Web application in any language supported by the .NET Framework. That includes Visual Basic, C#, J#, JScript, and others.
The recommended program to use is Visual Web Developer 2008.
Old projects will continue to run without change. In Visual Studio 2005, if you open a project created in Visual Studio .NET 2002 or 2003, the project is converted to the new project layout used in Visual Studio 2005. As part of the conversion, pages that use the old code-behind model are converted to use the new code-behind model. You cannot create pages using the old code-behind model in Visual Studio 2005.