AJAX Toolkit Mysterious Behavior

     I have been working with AJAX extensions for some time now.  I recently moved jobs and started working on a different project.  I remember that in my previous position I had a problem with Visual Studio 2008 working with AJAX and .NET Framework 3.5 SP1. I do not remember the problem or the fix but I resolved the issue originally. Now, here at me new job, I had the exact same problem.  What did I do this time you may ask?  I searched frantically around the web for a resolution because I didn’t remember what I did last time to fix the problem.  I found a lot of suggestions from removing wireless mouse (??) to reinstalling .NET 3.5 SP1 to restoring Visual Studio 2008 to initial install settings. None of which worked by the way.  I thought I would let you know this time what I did to remedy the problem.  First, the issue was I could not see the AJAX Toolkit in the VS toolbox.  I saw the AJAX Extensions tab and it was populated but no luck with the toolkit.  I had downloaded the AJAX binaries and extracted on my shared drive.  I included the toolkit on my web project and it did not work.  I tried several other things and to my disappointment didn’t work. 

The solution you ask: 

• Copy the ajaxcontroltoolkit.dll to a local folder on your c: drive.
• Then create a new tab and name it whatever you like (I named mine AJAX Toolkit).
• Then right click inside toolbox in VS and then choose items. 
• After the popup shows itself choose browse button and browse to newly placed .dll file. 
• The toolkit will start populating from there. 

It will work. Hope this helped someone.  Have fun coding and as always, if there are any questions or suggestions, they are welcome.  Thank you.

.NET and Coldfusion and IIS7 and Charting and AJAX and…

ARRGH!

     I am in the process of creating an application that uses the MS Charting controls along with some AJAX.  I was working on my machine of XP with VS 2008.  I didn’t have IIS installed so I was using built in browser functionality from VS to view site. Everything was going great. Was being the key word.  I had to finally move it over to a real development environment for more reasons than one.  When I finally moved the application it broke. It just wouldn’t work.  I got a 500 error.  Then after a few refreshes I found that I had this error: The WebResource.axd handler must be registered in the configurtion to process this request.  What!? What does that mean?  I searched for a few days to find a solution. I came up with a few from restarting the web service to reinstalling the .NET framework (none of which worked by the way).  After 4 days I finally came across the solution, Coldfusion does not play well with AJAX and .NET. For some reason, after looking at the compiled error logs, I saw that my appication was calling a .DLL in the Coldfusion directory.  Why on earth would my Microsoft .NET 3.5 SP1 application even be concerned with anything Coldfusion?  It seems that it is a mapping issue within IIS 7.  Yup, IIS 7. I had to remove (not sure if it was the right thing to do) but I removed all mappings to anything Coldfusion (.cfm, cfml, jsp, etc.).  It it was mapped to anything in the Coldfusion directory, I got rid of it.  Guess what?  It worked.  Application works like a champ now!  I am putting this up here so to be another resource to call upon.  There wasn’t anything I found that said to do what I did.  The closest I came was to have .NET and Coldfusion install on different servers.  Likely scenerio.  Yea right… Hope this helped someone.  Have fun coding and as always, if there are any questions or suggestions, they are welcome.  Thank you.