AsyncFileUpload to 2025v2 399

AsyncFileUpload to 2025v2 399

Posted by: enrique.pv-ext on 22 May 2026, 7:22 am EST

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 22 May 2026, 7:22 am EST

  Hi,
  
  Migrate from 2010v1 to 2025v2 399 in ASP.NET WebForms NET Framework 4.8.1.

  Using AsyncFileUpload legacy

  <%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="Ajax" %>
  
          <Ajax:AsyncFileUpload ID="FileUpload"
              OnClientUploadStarted = "uploadStarted"
              OnClientUploadError="uploadError" 
              OnClientUploadComplete="uploadComplete" 
              runat="server"  
              UploaderStyle="Modern" 
              UploadingBackColor="#CCFFFF" 
              ThrobberID="myThrobber3" 
              Width="400px"
              clientIdMode="AutoID" />
          

  any alternative new control C1 2025v2 399 for file upload ?

  thnaks a lot

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 25 May 2026, 9:06 am EST

  Hello Enrique,

  For ASP.NET WebForms, you may consider using the ComponentOne C1Upload control as an alternative to the AjaxControlToolkit AsyncFileUpload control. C1Upload supports asynchronous uploads, progress tracking, multiple file selection, client-side events, and file validation.

  Here is the documentation for C1Upload: https://developer.mescius.com/componentone/docs/webforms/online-upload/overview.html

  Regards,
  
  Uttkarsh.

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 5 June 2026, 6:33 am EST

  Can you full sample , and using Client-Side Events ?

  thanks a lot!

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 8 June 2026, 3:23 am EST

  Hello Enrique,

  For a complete sample, please refer to our ControlExplorer Product Sample located at:

  “C:\Users\uttkarsh.matiyal\Documents\ComponentOne Samples\ASP.NET Web Forms\WebForms\CS\ControlExplorer”

  This sample should be available on your machine if you selected the samples option while installing the C1WebForms Suite through ComponentOneControlPanel.

  If the samples are not installed, please repair the installation and make sure the samples component is selected for installation.

  Regards,
  
  Uttkarsh

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 8 June 2026, 3:57 am EST

  C:\Users\MYUSER\Documents\ComponentOne Samples
  
  only has C1Samples.json

  C1Samples.json

  {"Name":"ASP.NET WebForms Control Explorer Sample","Description":"The Control Explorer sample demonstrates features for all controls in Studio for ASP.NET Web Forms."
  
  ,"ReadMe":"C:\\TRABAJO\\ComponentOne\\Samples\\ComponentOne Samples\\ASP.NET Web Forms\\WebForms\\CS\\ControlExplorer\\readme.txt"
  
  ,"PreViewImage":"","_filter":null,"Filter":null,"IsVisible":true,"Samples":"","FrameWorkSamples":[{"FrameWork":""
  
  ,"LaunchCSharp":true,"LaunchVB":false,"OpenFolder":false,"Samples":"","LanguagedSamples":[{"Language":1
  
  ,"Solution":"C:\\TRABAJO\\ComponentOne\\Samples\\ComponentOne Samples\\ASP.NET Web Forms\\WebForms\\CS\\ControlExplorer\\ControlExplorer.sln","Samples":""}]}]}

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 8 June 2026, 5:32 am EST

  Hello Enrique,

  Thank you for sharing that. The C1Samples.json file you see is just a manifest that the ComponentOne Control Panel uses to track sample locations — the actual sample project files are separate and need to be installed.
  
  Based on your JSON, the installer expects the sample solution at:
  
  C:\TRABAJO\ComponentOne\Samples\ComponentOne Samples\ASP.NET Web Forms\WebForms\CS\ControlExplorer\ControlExplorer.sln

  Could you check if that path exists on your machine? If the files are not there, please try the following:

  Open the ComponentOne Control Panel

  • Select Repair for the ASP.NET Web Forms Suite
  • Ensure the Samples component is checked before proceeding

  Once installed, open the ControlExplorer.sln solution and look for the C1Upload sample to find a complete working example with client-side events.

  Regards,
  
  Uttkarsh