When do you plan on supporting
ASP.NET v2.0?
How do I switch my site from v1.1
to v2.0?
Does it cost anything to switch from
v1.1 to v2.0?
Can we have both versions
v1.1 and v2.0 of the framework installed on our site?
Can I switch my site back to v1.1?
Do you support Visual Studio 2005
and publishing files?
Do you support Visual Web Developer?
Do you support remote
debugging on my shared plan?
What is the connection string
information that I need to be able to use SQL Server?
What is the connection
string information that I need to use Microsoft Access?
I receive an error that
“LocalSqlServer” has already being defined. What do I do to resolve that?
Do you support the various
starter kits?
Do you support SQL Server
Express and XCopy deployment?
Can I configure the ASP.NET
database schema myself?
Does my connection string
need to change now that I am using ASP.NET v2.0?
Do you support SQL Cache dependency
introduced in ASP.NET v2.0?
Can I install my components in the
GAC (Global Assembly Cache)?
Q. When do you plan on supporting ASP.NET v2.0?
A. We currently support ASP.NET v2.0 on all our shared and shared webfarm plans and can switch a site over from v1.1 to v2.0 upon request. Upgrading to ASP.NET
v2.0 is available upon request for Dedicated and VM servers as well.
top
Q. How do I switch my site from v1.1 to v2.0?
A.
Send an email to
webteam@orcsweb.com and request for your website to be upgraded
to use the ASP.NET v2.0 framework. There is no cost to switch and there is only
a brief outage of less than one minute while we switch your site. Other sites on
the server won’t be affected in any way.
top
Q. Does it cost anything to switch from v1.1 to v2.0?
A. No, there is no cost to switch your site to use ASP.NET v2.0, nor is there a
charge to switch back if you wish to do so.
top
Q. Can we have both versions v1.1 and v2.0
of the framework installed on our site?
A. Generally we recommend against having both frameworks installed on the same site
however we can configure separate sub-folders or virtual directories with separate
framework versions.
top
Q. Can I switch my site back to v1.1?
A. Sure, you can switch your site back to v1.1. Just send an email to
webteam@orcsweb.com
and specify that you would like the framework switched back to v1.1. There will
be about 1 minute of outage while we switch your site back.
top
Q. Do you support Visual Studio 2005 and publishing
files?
A. Yes we do support all methods except for WebDAV when publishing files using Visual
Studio 2005.
top
Q. Do you support Visual Web Developer?
A. Yes we do support all features when using Visual Web Developer. Visit http://www.asp.net
for more information on how to download and use.
top
Q. Do you support remote debugging on my
shared plan?
A. No, remote debugging is not supported on the shared plans. We recommend that
you do your debugging on your development machine and deploy the website once it
has been tested and debugged
locally.
top
Q. What is the connection string information
that I need to be able to use SQL Server?
A. We have changed our global configuration files from the default so that they
use a connection string called “OWSqlServer”. This is so that it does not conflict
with the default “LocalSqlServer” connection string which many people use for local
development.
Here is a sample web.config file that should be placed in your root folder. Replace
the {variables} with your own database information.
<?xml version="1.0"?>
<configuration>
<connectionStrings>
<add name="OWSqlServer" connectionString="Server={sql server};
User ID={username};password={password};Database={database name};
Persist Security Info=True" providerName="System.Data.SqlClient"/>
</connectionStrings>
</configuration>
top
Q. What is the connection string information that I need to use Microsoft Access?
A. The same information applies to Microsoft Access as to SQL Server except that
the connection string is different. Note that Microsoft Access is not recommended
except for the most simple websites since it does not
handle many simultaneous connections well. Here is a sample web.config file for Microsoft Access. Replace the {variables}
with your own database information.
<?xml version="1.0"?>
<configuration>
<connectionStrings>
<add name="OWSqlServer" connectionString=""Provider=
Microsoft.Jet.OLEDB.4.0;Data Source={\somepath\mydb.mdb};
User Id=admin;Password=;" providerName="System.Data.OleDb"/>
</connectionStrings>
</configuration>
top
Q. I receive an error that “LocalSqlServer” has already being defined. What do I do to resolve that?
A. Even though we changed the default connection string used by the ASP.NET v2.0
database driven features to “OWSqlServer”, we left the connection string called
LocalSqlServer in place. This connection string does not point to a real database
but is used so that developer’s local machines, with the default settings, best
match the production servers. During beta testing we found that many users had “LocalSqlServer”
defined in their web.config files for development but when deploying, they ran into
a number of errors due to the differences between servers.
To resolve this, first you must ‘remove’ the connection string which is already
set in the machine.config file. Here is an example of how to remove the “LocalSqlServer”
connection string in machine.config and define your own. Note that this applies
to your local development the same way and is not specific to our servers.
<connectionStrings>
<remove name=”LocalSqlServer” />
<add name=”LocalSqlServer” connectionString=”
{connection string to your local database or the database that we
provide} providerName=”System.Data.SqlClient”/>
<add name="OWSqlServer" connectionString="Server={sql server};
User ID={username};password={password};Database={database name};
Persist Security Info=True" providerName="System.Data.SqlClient"/>
</connectionStrings>
top
Q. Do you support the various starter kits?
A. Most certainly. See other FAQ questions for further discussion on the LocalSqlServer
connection string name and how to best manage it.
top
Q. Do you support SQL Server Express and
XCopy deployment?
A. Due to security considerations in a shared hosting environment, we do not support
Sql Express. Instead, our Platinum Shared Hosting
Plan offers a SQL Server database which we can
prepare for you to support the ASP.NET v2.0 database schema.
top
Q. Can I configure the ASP.NET database schema
myself?
A. Sure. We can do this for you by request or you can do it yourself. To configure
your database to work with the database driven features of ASP.NET v2.0, locate
and run the file called aspnet_regsql.exe which is located at
%windir%/Microsoft.NET/Framework/v2.0.50727.
Follow the wizard and enter your database connection information. You will not be
able to use the dropdown list to select your database name with the db_owner permissions
assigned to you on a shared SQL Server. Instead type in your database name directly.
This will create a number of tables and stored procedures in your database which
ASP.NET requires for the database driven features.
Click here for an additional resource with a walkthrough that shows how
to do this.
top
Q. Does my connection string need to change
now that I am using ASP.NET v2.0?
A. No, the existing connection strings and database providers will continue to work
just as well.
top
Q. Do you support SQL Cache dependency introduced in
ASP.NETv2.0?
A. Yes, this is available if you have a SQL Server 2005 database. View our other
documentation for information on how to upgrade.
top
Q. Can I install my components in the GAC (Global Assembly
Cache)?
A. We do not support installing any components in the GAC on our shared web servers.
top