ASP.NET UpdatePanel Source Errors

Question

I have a problem with VS 2010, apparently losing the ability to load UpdatePanel in the middle of development, and it drives me crazy. I am using VS2010 and creating a user control with .NET 3.5 focused on DNN 5.x.

I created a control that will be used on the DNN website that uses the update panel. When I develop control using FTPing on a website and developing on it, everything works fine. I decided to move the development to a local copy of DNN and create a web application project for the control. At first everything worked fine. After several builds, I started getting the following errors:

The type or name of the namespace "UpdateProgress" does not exist in the Namespace 'System.Web.UI.WebControls.WebParts' (do you miss the assembly link?)

The type or namespace name 'UpdatePanel' does not exist in the namespace 'System.Web.UI.WebControls.WebParts' (are you missing the assembly link?)

I thought I messed up something and attached library links, so I unloaded everything and reloaded the library links. I kept getting the error and could not compile the control. Finally, I decided to redo the entire project and import the code that I already wrote. Everything worked fine until a few builds later, when the same error came out.

I did all the same things, unloaded links, reloaded them, and finally deleted the project. Every time I create a new project and copy the same code into .ascx files, they work fine ... for several collections. Last night I put together a library and tested the changes. Everything was great, so I closed the project and turned off the car. We turned it on this morning and got build errors. It looks like I have a ticking time bomb on my computer that just disables these things.

Any ideas on what I don't see that might cause this? I do not know why the library will flicker and exit like this. I have yet to face a similar problem with any other project on my local computer, and I really do not want to develop this through an FTP connection to the website, again. BLEH!

Answer 1

My decision fell into this strange state. This happened after editing the conflicts in web-config after receiving the last use of AnkhSVN. The error only appeared on the page that I opened in Visual Studio at that time. He said that he could no longer find UpdatePanel or UpdateProgress in System.Web.UI, which makes no sense, because I use these controls on my other pages.

Correction :
Just drag the UpdatePanel from the toolbar onto the page, throwing an error. Clean and rebuild, and you're good to go. All you have to do is delete the UpdatePanel that you added.
I believe that doing it again paves things in a decision that I could not see.

Answer 2

If you study the new web.config file, you will see the following (or something close). I was able to add this compiler directive without any other changes and successfully compile. ScriptManager is in the old version of the .dll extensions and needs to be linked. Creating a new site seems to add compiler directives, but there will be no update.

<!--/system.webServer positional notes-->; <runtime> <assemblyBinding appliesTo="v2.0.50727" xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> </assemblyBinding> </runtime> <!-- /configuration --> 

Answer 3

I had the same problem in all my old projects after upgrading to Framework 4.0. I have tried many times to find out why this is happening, and nothing I found will work. My team spent a year manually updating designer.vb for UpdatePanel to have the correct link every time we changed ASPX.

The problem is with the link to the AjaxControlToolkit project file. The link in the .vbproj file was for version 3.5. Therefore, simply updating the DLL did not update the link. The solution was to remove the AjaxControlToolkit link, save the project, and then add the link to AjaxControlToolkit.dll .

If you opened the project file in a text editor, you might have seen something like this:

 <Reference Include="AjaxControlToolkit, Version=3.5.60623.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e, processorArchitecture=MSIL> <SpecificVersion>False</SpecificVersion> <HintPath>bin\AjaxControlToolkit.dll</HintPath> </Reference> 

If you did everything right, it should look like this:

 <Reference Include="AjaxControlToolkit"> <HintPath>bin\AjaxControlToolkit.dll</HintPath> </Reference>