Installer Message

I had the .net framework installed on my computer and then installed Visual Studio 2005 and have been playing with ASP.net 2.0 for a while. Now that I downloaded the AJAX tool and try to install it I am getting a message that says I do not have the .net framework and AJAX cannot be installed to compatibility errors. I verified?in?my?programs?list?that?.net?framework?is?there?and?I?have?the?latest?(3.0)?all?the?way?back?to?1.0?so?I'm?not?sure?what's?going?on.?The?only?thing?I?can?think?of?is?that?Admin
privies are required to install b/c registries are being altered or something (I don't have admin). Normally when I try to use a windows installer and that happens I get an "Administrative Rights Required" message; not a compatibility message...Any thoughts?

Thanks!

JoeI had Tech Support give me admin privileges and the AJAX extensions installed without a problem. Apparently the installer was getting confused...it normally reports that sort of thing when Admin is required on an install.

Installing AJAX on a fresh machine

I have a requirement from a client that I will not be able to run the AJAX Extensions installer. Is there a list of what the installer does so that I can mimic it myself during deployment? If not, they're forcing me to go the Prototype route, and I don't want to do that.

Thanks for any advice.

Dan

Hi Dan,

Please try to get a copy the Ajax extension dll and install it into the GAC of the target computer withGacutil.exe

Installing AJAX Problems

Hi,

I'm trying to deploy AJAX on a production server. I've run the AJAX 1.0 Extensions msi installer and have verified that System.Web.Extensions/.Design v. 1.0.61025.0 are located in the GAC.

The website however tells me that the assembly wasn't able to be located:

Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.Source Error: Line 1:<%@dotnet.itags.org. Master Language="C#" AutoEventWireup="true" Codebehind="Site.master.cs" Inherits="BlackBox.Site" %>Line 2:<%@dotnet.itags.org. Register Assembly="System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"Line 3: Namespace="System.Web.UI" TagPrefix="asp" %>Line 4:<%@dotnet.itags.org. Register src="http://pics.10026.com/?src=StrategyStats.ascx" TagName="StrategyStats" TagPrefix="uc2" %>

When I copy System.Web.Extensions in my web application's bin folder I get:

Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)Source Error: Line 1:<%@dotnet.itags.org. Master Language="C#" AutoEventWireup="true" Codebehind="Site.master.cs" Inherits="BlackBox.Site" %>Line 2:<%@dotnet.itags.org. Register Assembly="System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"Line 3: Namespace="System.Web.UI" TagPrefix="asp" %>Line 4:<%@dotnet.itags.org. Register src="http://pics.10026.com/?src=StrategyStats.ascx" TagName="StrategyStats" TagPrefix="uc2" %>

Any ideas how to solve this?

Thanks

anyone? I'm a bit in a rush to get this solved for a production environment.

Thanks

Check your project references folder forSystem.Web.Extensionsand add it if it's not there.

Mine's referencing:
C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\System.Web.Extensions.dll

Good luck.

hmmmm ...

Why do you register that assembly again when it's already in the GAC? And it's probably in your Web.Config file already.

hmm... I didn't add those references, VS did when I added the Script Manager I think. However, when I take them out it works. Thanks!

Your project must have not been created asAJAX Enabled.

Another cool thing you may want to try is moving your AJAX tag prefixes to the web.config file. Try creating a new AJAX enabled website and examine the web.config for an example.

It actually was created as AJAX enabled Web Project and the web.config contains all the AJAX specific code. No clue why the register directives got added to the individual sites...