ASP.NET AJAX RC1

Discussion in 'ASP.NET 2.0' started by wisemx, Dec 15, 2006.

  1. when will DASP support/install RC1?
     
  2. Isn't there a GAC install requirement?
    Or has that been dropped in thie RC releaselike they (MS) said it was for the final release?

    BZ

    Post Edited (Buzzmaster) : 12/15/2006 11:13:26 PM GMT
     
  3. Bruce

    Bruce DiscountASP.NET Staff

  4. Hello to all,


    I'm new to Ajax. I liked Scott Guthrie's video demo at http://ajax.asp.net/, and I'm attempting to do an experiment here at DASP following that simple model. I simply want to see if I can use an UpdatePanel at DASP.


    I'm using a clean Visual Studio 2005. (Never had any Atlas/Ajax stuff on it before.)


    There are 3 main downloads available at the page of Scott Guthrie's video:
    1. ASP.NET AJAX 1.0 RC
    2. ASP.NET AJAX Control Toolkit (I ignored)
    3. AJAX Futures Dec CTP (I ignored)


    To keep things as simple and clean as possible, I chose to download onlythe first item,ASP.NET AJAX 1.0 RC, which I installed last night on my development laptop,very easily.


    I then made a small web application, similar to Scott Guthrie's demo. But before I put the AJAX functionality in it, I decided to deploy it to DASP so that I could observer the page flashing before hand. I published the tiny app to my DASP account, but when I try to run it, I get this error:


    Server Error in '/' Application.
    --------------------------------------------------------------------------------


    Configuration Error
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.


    Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (E:\web\citrusprice\htdocs\web.config line 60)


    Source Error:



    Line 58: </httpHandlers>
    Line 59: <httpModules>
    Line 60: <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
    Line 61: </httpModules>
    Line 62: </system.web>



    Source File: E:\web\citrusprice\htdocs\web.config Line: 60



    --------------------------------------------------------------------------------
    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42


    Can anybody give me some advice?


    Thanks in advance.
     
  5. The syntax is correct on line 60 for the current version.


    Try moving that to the root of your site, you can still use another web.config in any other folder as needed.
     
  6. Wisemx - Thanks very much for responding.

    My web.config is already inthe root of my site. I looked just now to make sure.

    Is this theline in the error message you're referring to?
    (E:\web\citrusprice\htdocs\web.config line 60)

    I don't know where the "htdocs" part comes from. It's not a part of my app.

    Any thoughts? Thanks.

    Polybius
     
  7. htdocs is the server path if you climb up past the root of your site.


    Can you post your entire root web.config?


    Comment out any sensitive info such as passwords, etc.


    All the best,


    Mark


    btw, are the dlls in your /bin/ folder? (Forgot to ask about that...)
     
  8. Mark -


    I did as you suggested, ie, put a copy of System.Web.Extensions.dll (version dated 12/11/2006) in the Bin directory.


    Now its working.


    Many thanks.


    Tim


    PS. Now I can see the page flashing. Next I'll try to implement the Ajax technique demo'd by Scott Guthrie in the video, to see if it eliminates the flashing.

    Polybius
     
  9. Awesome...Glad to see it's working.


    Merry Christmas[​IMG]


    Mark Wisecarver aka wisemx
     
  10. ok i have tried everything you suggested but i am still getting the same error he has and shouldnt the *.dll's already cahced on the DASP servers, I should not have to move them to the bin directory. i am so confused on this, it should not be this hard to get this to work.
     
  11. Thanks Vikram for the fast response.


    Yes my application is at the root and ihave made sure that i went and made the bin an application directory like i read on another posting.


    I will make sure those files are there, but againi ask why should i have to upload those files should they not already be in the assembly cache?





    Thanks,


    RGCS
     
  12. Hey guys,


    The way DASP is doing this is, I believe, the best for us.


    Current status:


    1) We have control over the Ajax controls, version and extension.


    2) The /bin/ folder DOES NOT need to be an application, it is the /bin/ location for your applications.
    3) When uploading files from Visual Studio use the Copy Website feature.
    During that operation you can sync the /bin/ folder by double-clicking on it in the Local side.

    If for example you place the latest Ajax and extender controls in your /bin/ folder and test them successfully...
    Once you get the proper web.config and /bin/ files on your remote server you're in business.

    Keep in mind the changes need to be made in your root web.config, the /bin/ folder and your code.
    Salute,
    Mark Wisecarver
     
  13. Good thread.


    The only thing I needed to put in my Bin is this file: System.Web.Extensions.dll


    I'll second Buzzmaster's suggestion. It seems to me that if we could talk DASP into registering System.Web.Extensions.dll into the Global Assembly Cache, thenI wouldn't have to upload that file every time I update my web application.


    I use Visual Studio 2005's Build/Publish feature to upload changes to my app, and it always must delete all files in my root first. Thus I end up having to manually re-upload System.Web.Extensions.dll after I make anychanges to my site.


    Maybe I'm not doing things the smartest way. Any thoughts anybody?


    Thanks.





    Polybius
     
  14. RGCS - No they do not need to be in the GAC.You can have them in your local bin directory.

    Vikram

    DiscountASP.NET
    www.DiscountASP.NET
     
  15. What you say there sounds practical, Mark.

    I'm very happy because Ajax is working well for me at DASP right now as things stand.

    I do need to start using the Copy Website feature.

    Thanks.

    Polybius
     
  16. [​IMG]


    Well mine is finally working ok now. After making sure the *.dll's are in my bin directory instead of counting on DASP to have them added to the assembly cache.


    Thanks for the help vikram
     
  17. Takeshi Eto

    Takeshi Eto DiscountASP.NET Staff

    Good to hear that everything is working for you. Please note that we do not install beta, RC or any pre-release stuff on production webservers. Also, Microsoft doesn't offersupport for any of their pre-release stuff.

    Eric
    DiscountASP.NET
    http://www.DiscountASP.NET
     
  18. That sounds like a very good policy, Eric. I have some other accounts in other places, and I'm fairly new here, but I sure like it here so far.


    Whatever it is you guys are doing here at DASP, the end result has so far been verygood it seems to me.


    Polybius
     
  19. I added 4 dll in "Bin" folder ..

    AjaxControlToolkit.dll
    AJAXExtensionsToolbox.dll
    Microsoft.Web.Extensions.Design.dll
    Microsoft.Web.Extensions.dll


    but it have error on web.config



    Security Exception Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

    Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Configuration.ConfigurationPermission, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' failed.

    Source Error:





    Code:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack Trace:





    Code:
    [SecurityException: Request for the permission of type 'System.Configuration.ConfigurationPermission, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' failed.]
       System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark&amp; stackMark, Boolean isPermSet) +0
       System.Security.CodeAccessPermission.Demand() +59
       System.Configuration.BaseConfigurationRecord.CheckPermissionAllowed(String configKey, Boolean requirePermission, Boolean isTrustedWithoutAptca) +65
    
    Web.Config Content :







    <configuration>





    <configSections>





    <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">


    <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">


    <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">


    <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />


    <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>





    </sectionGroup>


    </sectionGroup>


    </sectionGroup>


    </configSections>


    <system.web>


    <pages>


    <controls>


    <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add namespace="AjaxControlToolkit" assembly="AjaxControlToolkit" tagPrefix="ajaxToolkit"/>


    </controls>


    <tagMapping>


    <add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="System.Web.UI.Compatibility.CompareValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="System.Web.UI.Compatibility.CustomValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="System.Web.UI.Compatibility.RangeValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="System.Web.UI.Compatibility.RegularExpressionValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="System.Web.UI.Compatibility.RequiredFieldValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="System.Web.UI.Compatibility.ValidationSummary, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    </tagMapping>


    </pages>


    <compilation debug="true">


    <assemblies>


    <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></assemblies>


    </compilation>


    <httpHandlers>


    <remove verb="*" path="*.asmx"/>


    <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"/>


    </httpHandlers>


    <httpModules>


    <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    </httpModules>


    </system.web>


    <system.web.extensions>


    <scripting>


    <webServices>


    </webServices>





    </scripting>


    </system.web.extensions>


    <system.webServer>


    <validation validateIntegratedModeConfiguration="false"/>


    <modules>


    <add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    </modules>


    <handlers>


    <remove name="WebServiceHandlerFactory-ISAPI-2.0"/>


    <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    <add name="ScriptResource" verb="GET" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>


    </handlers>


    </system.webServer>


    </configuration>



    please help me



    Post Edited (hamidreza) : 1/11/2007 5:56:40 PM GMT
     
  20. Try setting requirePermission='false' for each of the section declaration.

    i.e
    <sectionGroup name='webServices' type='Microsoft.Web.Configuration.ScriptingWebServicesSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'>
    <section name='jsonSerialization' type='Microsoft.Web.Configuration.ScriptingJsonSerializationSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' requirePermission='false' </font>/>
    <section name='profileService' type='Microsoft.Web.Configuration.ScriptingProfileServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' requirePermission='false' </font> />
    <section name='authenticationService' type='Microsoft.Web.Configuration.ScriptingAuthenticationServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' requirePermission='false' </font> />
    </sectionGroup>

    Vikram

    DiscountASP.NET
    www.DiscountASP.NET
     

Share This Page