Your application requires that you install Microsoft Ajax in addition to
.Net 2.0
This is available from http://www.asp.net/ajax/
--
Rory
WhiskeyRomeo - 30 Oct 2007 16:59 GMT
Thanks for the quick reply. Just to be clear. We need to install the same
Ajax Extension 1.0 for the production machine as I did for the development
machine?
> Your application requires that you install Microsoft Ajax in addition to
> ..Net 2.0
[quoted text clipped - 3 lines]
> --
> Rory
Rory Becker - 30 Oct 2007 17:35 GMT
> Thanks for the quick reply. Just to be clear. We need to install the
> same Ajax Extension 1.0 for the production machine as I did for the
> development machine?
Thats what I hear, although I have not done this myself as I have only just
started looking at ajax myself recently.
--
Rory
WhiskeyRomeo - 30 Oct 2007 18:02 GMT
That didn't make a different. Here is the error in the event log. This is
beyond my skill and link it gives doesn't provide any help.
It is not possible to run two different versions of ASP.NET in the same IIS
process. Please use the IIS Administration Tool to reconfigure your server to
run the application in a separate process.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
> > Thanks for the quick reply. Just to be clear. We need to install the
> > same Ajax Extension 1.0 for the production machine as I did for the
[quoted text clipped - 5 lines]
> --
> Rory
WhiskeyRomeo - 30 Oct 2007 19:49 GMT
My apologies, that did work for the problem you were answering. But I had to
create a different application pool for 2.0 applications to run in in IIS.
That solved all my problems.
Thanks for the help.
> > Thanks for the quick reply. Just to be clear. We need to install the
> > same Ajax Extension 1.0 for the production machine as I did for the
[quoted text clipped - 5 lines]
> --
> Rory
Rory Becker - 30 Oct 2007 21:24 GMT
> My apologies, that did work for the problem you were answering. But I
> had to create a different application pool for 2.0 applications to run
> in in IIS. That solved all my problems.
Excellent ... glad to hear it.
--
Rory
As Rory has mentioned, you will also have to install AJAX. Rather than just
kudos, here are a few other "hints".
1. Use publish and publish to a local folder before deploying. It will only
leave the files necessary
2. If you want less "stuff" out there, consider web application project
instead of websites. This will compile down much more compactly than normal
publish
3. Some of the linked files in web.config are not necessary. This particular
error cannot be cured by deleting from web.config (will create another one),
but some can.

Signature
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
*************************************************
>I am trying to copy files and folders onto a production machine (Windows
>2003
[quoted text clipped - 36 lines]
> Culture=neutral,
> PublicKeyToken=31bf3856ad364e35"/>
WhiskeyRomeo - 30 Oct 2007 18:33 GMT
Thanks for the reply. See my last response to Rory. I have a generic
website whose root directory is nothing but html. I have 1.1 application in
separate folder in this root directory. I was hoping to simply include a 2.0
application under the same root directory but that appears not to be possible
because the website itself must specifiy an ASP.Net version.
Bill
> As Rory has mentioned, you will also have to install AJAX. Rather than just
> kudos, here are a few other "hints".
[quoted text clipped - 51 lines]
> > Culture=neutral,
> > PublicKeyToken=31bf3856ad364e35"/>