Microsoft.Web.* References that are required to build the projects are not visible when you select References -> Properties from withing VSTS.  There are no Microsoft.Web.UI etc added after the installation of the BETA 1.

 

When I did the install - the installer found the CTP version and so exited.  De-installed the CTP msi, and re-ran the setup. I did explicitly check *Everyone as the installment option.  I figured since I had VSTS open during the install - I did a reboot and a repair and same symptoms. 

Documentation states that it is not supported to add the files to the bin of the project so what needs to happen?  Running XP Pro.

 I do have the Microsoft.Web.Extensions PKT:31bf3856ad364e35 version 1.061025.0 both zap and gac but can not add that either from VSTS for project reference unless I use the browse function...I have no other Microsoft.Web.* other than Microsoft.Web.Services3 (which is for WCF I believe).

 The ToolKit Example does run however but it doesn't use the coding model I use as all of my code is in project assemblies and ascx files are loaded dynamically....

 

 

 

 

 

 

 

 

I've got the same issue here. I've made all of the changes to the web.config, removed the old Microsoft.Web.Atlas.dll from the bin director and from the project references, but the project won't compile because it can't find any Microsoft.Web namespaces, which makes sense because Microsoft.Web.Extensions is not referenced and although it is in the GAC, it does not show up in the Add References dialog.

I haven't tested it but the Microsoft.Web.Extensions.dll is located in the %Program Files\Microsoft ASP.Net\Asp.Net 2.0 Ajax Extensions % dir...

 

I manually added it to my project(s)... 

 

It now at least tries to compile without the namespace error...  can't see if the issues with the docs saying not to copy it to the bin directory means it won't run during runtime - but nonetheless I can't see why it can't be done if its not being ref from the GAC.  However, I do imagine that when it comes time to test it - at this rate will have to copy - delete depending on whether testing the app or dev work. 

 

 

I just copied the dll into bin directory and referenced it there just like before.  It seems they might have forgotten about those of us using the Web Application project type with this Beta release.

Are you saying that you placed Microsoft.Web.Extensions.dll in the Bin folder of the web site in this case? This assembly should be GAC'ed during install. If you place the assembly in Bin then, I think you'll need to have the app in full-trust.

I did, as there is no way currently to make reference to the assembly in the GAC in a Web Application project.  The assebly is not listed in the add reference dialog.  I added the dll to the bin directory and reference it directly there just as in the CTP.

If there is another way to get this working I'm open to suggestions.

This is a bug - when we install, we don't add the registry entry necessary for Visual Studio to find and add the assembly to the Add References dialog. VS uses the file system to find assemblies.

To see it, add the following registry key

 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\ASP.NET AJAX 1.0.61025

and set its default value to the directory in Program Files that contains the DLL. Note: This can't include %Program Files%, and must have the physical drive letter and location. For example, on the default C: drive installation, it is

 c:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025

 We'll fix this in the next refresh.

Thanks,

Thank You.  That works for adding the reference to the project.  However, I'm still running into an issue that I am not sure if it is related or not.  The application compiles and seems to work at run-time however when viewing a page in the designer it does not recognize any of the ASP.NET AJAX controls, such as the UpdatePanel. I'm getting the "Element 'UpdatePanel' is not a known element".  I have made all of the necessary changes to the web.config file including this section which I believe is relevant to this problem:

 

		<pages>
			<controls>
				<add tagPrefix="asp" namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagPrefix="asp" namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagPrefix="atlas" namespace="Microsoft.Web.Preview.UI" assembly="Microsoft.Web.Preview"/>
				<add tagPrefix="atlas" namespace="Microsoft.Web.Preview.UI.Controls" assembly="Microsoft.Web.Preview"/>
			</controls>
			<tagMapping>
				<add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CompareValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CustomValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RangeValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RegularExpressionValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RequiredFieldValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="Microsoft.Web.UI.Compatibility.ValidationSummary, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
			</tagMapping>
		</pages>

 

Any idea what the problem with that might be?

"Are you saying that you placed Microsoft.Web.Extensions.dll in the Bin folder of the web site in this case? This assembly should be GAC'ed during install. If you place the assembly in Bin then, I think you'll need to have the app in full-trust."

 

I did... and yes you are right you will get Medium trust issues... I simply commented out the <trust level="medium" > in the web.config and all works well without doing fix mentioned in the post...

Make sure you are giving the UpdatePanel the correct prefix in your aspx / ascx page

 

it should now be <asp:UpdatePanel  >

 

Also note that MODE is now UpdateMode.

 

If referencing from code behind you need to import Microsoft.Web.Preview and Microsoft.Web.Preview.UI  (also add the Microsoft.Web.Preview.dll to your project bin.....

 

 

 

Yea, I'm set on those things.  Here is an example of a declaration that is giving me unknown element issues:

 

<asp:UpdatePanel ID="updAccount" UpdateMode="Conditional" runat="server">

 

 

have the same problem here with the update panel..

anyway it works ok 

my def is:

<asp:UpdatePanel ID="UpdatePanel1" runat="server">

 
 

We posted a document with the server side changes in the following link http://ajax.asp.net/files/Migration%20Guide.doc

 

It SEEMS to work but Everything within the Update Panel is not recognized and Intellisense is gone for all the normal web Controls within the Update Panel!

 

I have been trying for the whole day to get a site working cleanly!

 

My would the DEV team Change everything now?

 

Also if you only get 4 controls with the Extensions

if you want the other ATLAS control like Progress you have to add manually a reference to: Microsoft.Web.Preview.dll.

Why o Why 

 

AndresS:

We posted a document with the server side changes in the following link http://ajax.asp.net/files/Migration%20Guide.doc

 

 I have already done everything described in that document unfortunately.