You searched for the word(s): userid:706884

More Search Options

RSS Available

• Re: help me

  Like the previous poster has said, the server hosting your site probably doesn't have asp.net 3.5 installed and when your application tries to load the AJAX 3.5 assembly, it bombs. I am not sure how your host is setup but if they allow full trust, you can possibly try upload the AJAX 3.5 dll into the bin.

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/24/2009

• Re: Need urgent help for deployment

  Another potential problem is that your domain name's DNS is not pointing to your hoster's.

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/24/2009

• Re: web.config of subdirectory

  see http://www.aspdotnetfaq.com/Faq/how-to-disable-web-config-inheritance-for-child-applications-in-subfolders-in-asp-net.aspx

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/24/2009

• Re: File types

  Are you using IIS 6.0? With IIS 6.0, ASP.NET authentication only works for ASP.NET file by default. To protect other filetype, you'll have to create a script map on IIS to point that file extension to ASP.NET ISAPI. You can also setup wildcard mapping to point to asp.net.

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/24/2009

• Re: Uploading (copying) Database files to Server

  If customError is already set to "Off", and you are still getting the same custom error behavior. The problem could be 1) Make sure you set custom error to "Off" with a capital O. It is case sensitive. 2) Your web.config may have problem. If the web.config is malformed, asp.net will use the inherited settings.

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/23/2009

• Re: Could not load file or assembly 'Microsoft.SharePoint'

  Well.. according to the error, the global.asax is trying to load this assembly. If your project doesn't use this, remove this line in your global.asax file <%@ Assembly Name="Microsoft.SharePoint"%>

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/23/2009

• Re: Error trying to deploy my web app to test

  Your connection string is set to use windows security which means it will use the ASPNET user to connect to the database. It will not work in most production environment. I can 't really provide further help because I don't know how your SQL server is setup. You should ask the database admin to set up a SQL login and update your connection string. see http://www.connectionstrings.com/

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/19/2009

• Re: How to configure connection string to connect to SQL Server 2005 using a Windows domain account

  When you use "Trusted Connection", it means that ASP.NET will use the ASPNet user (or the impersonated user) to connect to the database. By default, IIS runs with a local account (Network Service on IIS7). To fix the problem, you can either change the IIS appPool user to the domain account you created or you'll have to programatically impersonate. In general, using Trusted Connection is a pain with ASP.NET application. I recommend you use SQL login if possible.

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/17/2009

• Re: How to move SQL Database from Local Sever to Hosting Server (Remote)

  This is a "limitation" with Management studio; unlike SQL Enterprise Manager (SQL2000), copy database only copy table / data but not views / stored proc etc. In general, there are several ways to publish your database to your hoster depending on what they support 1) MDF File attachment. Some hosters allows you to upload a detached MDF file to the server and they will attach it to the DB server for you (either manual or automated) 2) Restoration. Some hosters allows you to upload a database

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/17/2009

• Re: Question about automatic compilation.

  When your app gets the first request, ASP.NET compiles the application (code file / dll in bin) and store it in a temporary location (default is c:\Windows\Microsoft.NET\Framework\versionNumber\Temporary ASP.NET Files) See http://msdn.microsoft.com/en-us/library/ms366723.aspx for more detail technical explaination.

  Posted to Configuration and Deployment (Forum) by Bruce L on 11/17/2009