Attempting to deploy Demo version to server failing

  •  04-16-2009, 7:21 AM

    Attempting to deploy Demo version to server failing


    Hi     I recently downloaded the demo, got it working on my local desktop machine and am attempting to move it to the webserver to test the demo deployment.  However i am recieving the following error.  Here is what i have verified.

    using asp.net 3.5  C#

    1) The Bin folder contains the license file as well as the .DLL file
    2) the web config file contians the ....
         <httpModules>
          <!-- UploadModule is optional , for the property Uploader.ShowProgress -->
          <add name="CuteWebUI.UploadModule" type="CuteWebUI.UploadModule,CuteWebUI.AjaxUploader"/>
        </httpModules>
    3) the page calling the uoloader contains at the top:
          <%@ Page Language="C#" %>
          <%@ Register Namespace="CuteWebUI" Assembly="CuteWebUI.AjaxUploader" TagPrefix="CuteWebUI" %>

    but i still recieve the following error...
    is there anything else i should check for/do?


     

    Parser Error

    Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

    Parser Error Message: Could not load file or assembly 'CuteWebUI.AjaxUploader' or one of its dependencies. The system cannot find the file specified.

    Source Error:
    Line 1:  <%@ Page Language="C#" %>
    Line 2:  <%@ Register Namespace="CuteWebUI" Assembly="CuteWebUI.AjaxUploader" TagPrefix="CuteWebUI" %>
    Line 3: 
    Line 4: 

    Assembly Load Trace: The following information can be helpful to determine why the assembly 'CuteWebUI.AjaxUploader' could not be loaded.
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. 
    
View Complete Thread