works locally, but customErrors when deploying....

I've created a small website using ASP.Net 2.0 w/ Masterpage. The site compiles and runs fine locally from my machine (I have VS 2005 Beta and 2.0 Framework 2.0 Beta 2). But when I copy the whole application and paste to the development server, I get this error:
Server Error in '/intranet' Application.

---

Runtime Error

Description:An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="Off"/> </system.web></configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web></configuration>

I checked my Web.config and I do have <customErrors mode="Off"/>
Before, when I used VS 2003 it was running fine both locally and on the development server.
I'm wondering, do I have to install new Framework 2.0 Beta 2 on the development server as well?
Also, I look in my Bin folder, I only see "AspxLab.WebControls.dll" which is a menu component that I use for my site, but there's no other compiled dll for the site. Is this b/c of the new version of asp.net or am I missing dll file somewhere?

Hi Titi,
You need to make sure that you have the .NET Framework Beta2 installed on your remote server, and that you have that site configured to use it, when you deploy your app. Otherwise you'll get an error (probably the one above).
Note that if you have access to the remote server, you can also see a detailed error message if you access the page from a browser on the local server machine. That is one way to help figure out if you still have problems configuring things the first time.
Hope this helps,
Scott
Thanks for your help Scott, I'll ask the admin to d/l the framework beta 2 for us.