Let me start out by saying installation thus far has been easy.  I followed the instructions, but when I go to the Login screen I get the following error:

Parser Error

Line 21:   <div id="allContent">
Line 22:   <form id="form1" runat="server">
Line 23:   <asp:scriptmanager ID="scriptManager" runat="server" EnablePartialRendering="true" />
Line 24:   <div id="headerRegion">
Line 25:         <div class="welcomePanel">

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433  

 I go to my hosting page control panel and look at the extension that my site is using.  It says that I am using 2.0.  When I change it to 1.1, I get past that error and then I get the following error:

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Hi, I have a guess. try this:

Either get you the AJAX Extensions 1.0 

If 2.0 < .NET < 3.5 

or

use .NET 3.5

check out this: http://asp.net/ajax/downloads/

Thanks!!!

I agree - ensure your hosting provider has the Ajax Extensions 1.0 installed - the Technology page has all the prerequisites.

Forgive me 'cause I'm fairly new, joined today, but was wondering why the AJAX references are being pointed to the GAC to being with? Is this an application need? There is really no reason to mandate the environment have AJAX extensions installed when you can control this via the app's local references.(In the same vein that assemblies like Log4Net.dll are referenced). 

Maybe there is a very good reason, like migration path to .Net 3.5 or something. So not trying to question design, just curious. If the web app makes a local AJAX reference, then it takes the burden off making sure host admins get the right stuff installed. (of course this will no longer matter if DashCommerce is migrated to ASP.Net 3.5)

 Very cool product!

 Thanks,

T 

• When AJAX extensions are installed they fly to GAC. 
• This makes refererences centralized and simplified.
• When you copy/download a Project you don't need to download big big files of the refererences with it rather you just copy the References' Pointers.
• References' Pointers are written to the web.config/Project file of an application.

Thanks for your response. 

My point is you do not have to do it the way you described. Based on all the trouble users are having with AJAX 1.0 extensions references, it would be easier to change the web project's references to use non-GAC'd copies of the AJAX extension assemblies, and deploy those, along with the web project, in the "bin" directory.

Everyone, I don't know what I did, but I rebuilt the solution and uploaded the web piece to my host and everything is working like it should.  Sorry for all the fuss.