UpdateProgress Template and the Control Toolkit

I have an

atlas:UpdateProgress Template on the same page as some cascading drop downs. I have put in a large (5 seconds) delay on the webservice populating the dropdowns but still don't see the ProgressTemplate.

Does the UpdateProgress Template work with the control toolkit or is it just for UpdatePanels?

The Toolkit controls do not natively work with Atlas's UpdateProgress control. I looked into this briefly just now and it doesn't seem like the UpdateProgress control can be used in this way. Rather, it seems to tie itself directly to the "in postback" status of the relevant page. Since there are no postbacks in the CascadingDropDown scenario, UpdateProgress doesn't seem relevant. Sorry about that!

Updating Atlas

Hello,
I was developing a produciton project using Atlas July CTP and Control Toolkit.
Now I'd like to updating to last version, but I can see that ATLAS is formed by 2 components:
Atlas 1.0 beta AND Atlas CTP beta.
I was used only Updatepanel in July CTP

What I need now? Is necessary to install both 1.0 and CTP?

And fot update what I do?
Must uninstall the previous version and then Install the new one?

tnx

If you just used the updatepanel, you don't need the CTP Beta, only the AJAX.net 1.0 beta. If you used the Atlas Control Toolkit, you'll need to reinstall that too. You'll also have to update your pages to work with new new edition of the framework, but with just updatepanels, it won't be that hard.
Can some direct me to installation instructions page......please.

For install instructions, go to:

http://ajax.asp.net/docs/Overview/installing/default.aspx

For changes between ctp and beta, go to:

http://ajax.asp.net/files/AspNet_AJAX_CTP_to_Beta_Whitepaper.aspx?tabid=47

For a feature matrix of what is in each install, go to:

http://ajax.asp.net and click on Feautre Matrix in tabbed panels.

Updating atlas and toolkit

If you already have atlas installed and created a new application via the atlas template in visual studio and are using the atlas "controls" how do you do upgrades when new releases of atlas or the controls come out? Will the new setup files update your system (templates,controls and apps) or is there something else that you will have to do?

You'll just need to copy over the Atlas assemblies in your \bin directory, and potentially update the Atlas settings in the web.config file.

Hope this helps,

Scott

Updating control toolkit

I have some projects with some control from Atlas control toolkit (previous version).
Now there's the new version!
Is not easy to know what i do for update the previous with the new one.
Only change the dll?
It is sure that the old project will work? ...or I must to modify some code?
And what about .net controls tool list?
thanks

Just make sure that your project references the new dll. For the toolbox, delete all the controls from your toolkit tab and then readd them all. As for breaking changes, I've not heard about any, but I've not looked hard for a list of changes / breaking code.

Upgrade to Beta 1 = New Rating control error

I installed the latest framework and toolkit.

My project was working fine with a wizard control that contained rating controls. I've taken the rating controls out of the wizard template and put them in their own update panel and still receive the error. It's a very strange behavior. If I make a new page and do everything, the rating control works fine. I'm using the latest control and did all the changes required to use the new Beta. After the install, I keep receiving this error when loading the page:

System.InvalidOperationException was unhandled by user code
Message="The TargetControlID of '_RatingExtender' is not valid. The value cannot be null or empty."
Source="Microsoft.Web.Extensions"
StackTrace:
at Microsoft.Web.UI.ExtenderControl.RegisterWithScriptManager()
at Microsoft.Web.UI.ExtenderControl.OnInit(EventArgs e)
at AjaxControlToolkit.ExtenderControlBase.OnInit(EventArgs e) in C:\Program Files\Microsoft ASP.NET\AjaxControlToolkit\AjaxControlToolkit\ExtenderBase\ExtenderControlBase.cs:line 338
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.ControlCollection.Add(Control child)
at Microsoft.Web.UI.UpdatePanel.SingleChildControlCollection.AddSingleChild(Control child)
at Microsoft.Web.UI.UpdatePanel.AddContentTemplateContainer()
at Microsoft.Web.UI.UpdatePanel.CreateContents(Boolean recreate)
at Microsoft.Web.UI.UpdatePanel.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Thanks

Anyone ? Can you please take a look? I believe others are experiencing something similar with the mentioned TargetControlID.

Thanks

When the project breaks, it breaks at the bold:

/// <summary>
/// On Init we load target properties values and process databinding handlers.
/// </summary>
/// <param name="e"></param>
protected override void OnInit(EventArgs e)
{
if (EnableClientState)
{
CreateClientStateField();
}
// EnsureProfileScriptService(ScriptManager.GetCurrent(Page), true);
Page.PreLoad += new EventHandler(Page_PreLoad);
base.OnInit(e);
}

Please reply with acomplete, self-contained sample page that demonstrates the problem. Thank you!

In my case the problem occures when I specify the rating control in the skin file.

Skinfile:

<

ajaxToolkit:Ratingrunat="server"StarCssClass="ratingStar"WaitingStarCssClass="savedRatingStar"FilledStarCssClass="filledRatingStar"EmptyStarCssClass="emptyRatingStar"/>
Good to know! Do you have a complete, self-contained sample we can play with?

Just add the following 2 lines in the Default.skin file of the Ajax Control Toolkit SampleWebSite:

<%@.RegisterAssembly="AjaxControlToolkit"Namespace="AjaxControlToolkit"TagPrefix="ajaxToolkit" %>
<ajaxToolkit:Ratingrunat="server"StarCssClass="ratingStar"WaitingStarCssClass="savedRatingStar"FilledStarCssClass="filledRatingStar"EmptyStarCssClass="emptyRatingStar"/>

Then try to open the Rating sample of the SampleWebSite.

The SampleWebSite doesn't have a Default.skin file - might there be something else going on here that's causing issues?

upgrade to the new release of control toolkit provides versioning trouble

Hi,

I just copied and pasted the new dll of the control toolkit over the old ones. Then i changed the app.config to reflect the new version number :

<addtagPrefix="ajaxToolkit"namespace="AjaxControlToolkit"assembly="AjaxControlToolkit, Version=1.0.10606.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e"/>

I also removed all the icons from the toolbox and added them in again.

when i drag an item from the toolbox onto my form, it gives it the tag prefix of cc1 instead of ajaxToolkit.

like

<cc1:TabPanelID="TabPanel1"runat="server">

</cc1:TabPanel>

What is it that i am missing?

Thanks!

It is perfectly normal.

Refer to the following post for more details

http://forums.asp.net/p/1117736/1736819.aspx#1736819

Thanks for the reply and the link. According to the book that you link to, the developers need to add[assembly:TagPrefix("AjaxControlToolkit ", " ajaxToolkit ")] to theAssemblyInfo.cs file for this problem to go away.

First of all, it is not a problem. You don't need to worry about the tag prefix used by the controls.

The tag prefix is decided by the developer of the control. He makes the entry into the AssemblyInfo.cs of the control.

Upgrading Ajax Control Toolkit

Is there a faq on how to upgrade an existing app to a newer version of the control toolkit? What needs to be done etc?

Replace the old toolkit dll reference in your project(s) to the dll from the current release.

Seethis forum post for more details.

Upgrading the AJAX Control Toolkit?

If I have a directory called AJAXCTPEnabledWebsite1 in my VS websites folder, how do I upgrade that to the release version? I guess I'm not sure what the difference is between AJAX 1.0 and the AJAX Control Toolkit. If I have the AJAX Control Toolkit, does that mean I already have AJAX (pre 1.0 in my case) installed?

I just need to get upgraded to the release version(s) and need a little direction. Any help will be greatly appreciated. Which of these do I need:

http://ajax.asp.net/downloads/default.aspx?tabid=47

You needboth, the RTM version of ASP.Net AJAX and the latest version of the toolkit. You will need to recompile your project against the latest bits and check for any issues. You can find toolkit breaking changes information under thearchived releases section of the toolkit and ASP.Net AJAX breaking changeshere.

The latest version is v1.0.10301.0. Download that release (its the latest one), get the zip files that includes all the files. In the Sample Websites/Bin you will see "AjaxControlToolkit.dll". Thats the dll you need to import in to your VS Toolkit.

kirtid:

You needboth, the RTM version of ASP.Net AJAX and the latest version of the toolkit. You will need to recompile your project against the latest bits and check for any issues. You can find toolkit breaking changes information under thearchived releases section of the toolkit and ASP.Net AJAX breaking changeshere.

So is the 'beta' of the control toolkit the ASP.NET AJAX RC or the ATLAS version? I found the migration docs, but they are different based on which version you have. As I said, I have the 'beta', but I'm not sure if that is the same as the AJAC RC or the ATLAS version. I believe it should be the AJAX RC, but I want to confirm before I start uninstalling/installing. In the link below, it mentions 'beta' in the sentance above two possible documents, but the links and info about the actual links don't label either one as migration from the 'beta'.

Specifically, on this page, do I use the first or second migration document if I have the Control Toolkit 'beta'?: http://ajax.asp.net/documentation/default.aspx?tabid=47

Thanks for the info.

The toolkit is built on top of the ASP.Net AJAX platform. They are two separate entities. ASP.Net AJAX RTM is what the latest version of the toolkit uses. You should always use the latest version of the toolkit which is what we support. I pointed you to the archived releases in case you wanted to check out any older breaking changes. You should uninstall all older versions of ASP.Net AJAX before installing the RTM build, then download the latest version of the toolkit and compile your project against these new dlls.

Ahh, OK, now I see, that makes sense. Thanks!

Urgent! Need a asp.net Ajax enabled TreeView control

Hi,

I need a asp.net ajax enabled TreeView control, its not a part of the AjaxControl Toolkit. I need to know where from I can get it.Please let me know if any of you have come accross a one.

Thanks in advance,

Subhadip

http://www.google.be/search?hl=nl&q=treeview+ajax&btnG=Zoeken&meta=

Lots over there ;)

Kind regards,
Wim

Use Ajax Control Toolkit without .NET?

Hello,

I couldn't find any (good) documentation about the Ajax Control Toolkit and would like to know if it can also be used independently of the .Net framework, e.g. with php or java on the server.

thanks, luke

Hey,

No, it requires the ASP.NET AJAX extensions, which has to use .NET. You may be able to find a port for Mono; don't know anything about that.