AsyncFileUpload control generates MissingManifestResourceException

Mauricio

I have an C# - ASP.NET WebForm solution in Microsoft Visual Studio 2012 Professional; this solution is built in Framework 3.5 and this solution uses AjaxControlToolkit - version 3.5.40412.0.

I have a WebForm - which is a child of a Site.master - that uses multiple UpdatePanel, TabContainer and a single AsyncFileUpload.

Locally (i.e. in developer enviroment), the WebForm loads and works successfully, but, once published the WebForm in an different server - when a file is selected (by using the AsyncFileUpload control), the following message shows:

Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "AjaxControlToolkit.Properties.Resources.resources" was correctly embedded or linked into assembly "AjaxControlToolkit" at compile time, or that all the satellite assemblies required are loadable and fully signed.

In my local developer enviroment, this error does not occur and the file can be selected and processed as expected.

My Site.master already has the ToolkitScriptManager control, but, for some unknown reason, the error described above shows when a file is selected with the AsyncFileUpload control.

I've searched a lot in internet and in all of those sites, the single answer is: add ScriptManager or ToolkitScriptManager at the beginning of the WebForm / Site.master.

I can't find a reasonable explanation about why in other server(s) - tested in (2) different servers - this error appears.

I'm already out of options - since I can't replicate this error locally (enviroment PC).

Can anyone provide more information about how can debug and fix this issue?

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Mauricio5y ago
Thank you, Sachin, the first link is actually my account on Stack Overflow - I've posted this same question on different programming sites.

The second link you posted might solve the issue, but I have no physical access to the server(s) and the rest of the AjaxControlToolkit components works just fine - I suspect it's something else - it might be about legacy dependencies of some sort, but, I just couldn't solve this issue with AsyncFileUpload.

Here, I describe the solution I was able to produce: https://stackoverflow.com/a/65438736/12511801

Extract:

I couldn't solve the problem with the AsyncFileUpload control, but, as a good side, while searching about how to solve this issue, I tried again changing the code and use both FileUpload and UpdatePanel controls.

I changed my code for (instead using AsyncFileUpload) for use FileUpload inside a UpdatePanel, but, here is the catch:

For select and send the file to the server side, the Button that sends the file (once selected with the FileUpload control) must have its own UpdatePanel with its respective Triggers tag.

Example:

In the .aspx:
"updPnlbtnFileUploadDevols" runat="server">



        "btnLoadClassFileDevoluciones" runat="server" Text="Cargar Archivo"

            CssClass="chxbx" ForeColor="Teal" OnClick="BtnLoadChargeFileDevoluciones_Click" ValidationGroup="valChrgFileDevoluciones" CausesValidation="true" />





        "btnLoadClassFileDevoluciones" />
In the .aspx.cs:

///


/// Load file.

///

/// sender

/// e

protected void BtnLoadChargeFileDevoluciones_Click(object sender, EventArgs e)

{

    try

    {

        if (fupld_cargue.HasFile)

        {

            // Here, the file is detected in server-side

            // and it's been handled as logic demands it.

        }

        else

        {

            // File not detected in server-side.

            MessageBox("Please, select a file");

        }

    }

    catch (Exception handledException)

    {

        // Omitted exception-handling code in this sample.

    }

}
With the previous explanation, I finally could solve the issue I had about sending a file using FileUpload - which was inside an UpdatePanel control.
Sachin Singh5y ago
check the configuration file in development server and match it with config of production server
you need to have these assemblies in production as well
refer this two threads
https://stackoverflow.com/questions/65394404/problem-with-asyncfileupload-in-webform-after-being-published-in-server-aja
https://stackoverflow.com/questions/9230077/ajaxcontroltoolkit-not-working-after-publish-asp-net-c-sharp