Showing posts with label ctp. Show all posts
Showing posts with label ctp. Show all posts

Monday, March 26, 2012

Confused about Atlas July CTP and now AJAX Beta 1

I've been using the Atlas July CTP for my projects along with the Control Toolkit. Now I hear about AJAX Beta 1 (they scrapped the name Atlas right?)
If I wanted to update to AJAX Beta 1, how can I do so? I haven't seen any information about it so far.

Forgive me for my lack of understanding about this, but I'm kind of confused Embarrassed

Thanks!

Atlas was just a code name, it's now the Microsoft ASP.NET AJAX Extensions. If you go tohttp://ajax.asp.net/ there are several downloads as well as migration guides to switch you over from the previous CTPs to the new 1.0 beta. Click the Get Started tab at the top to... get started!

Thanks,

Eilon


Ok thanks that got me started!

But i'm having some problems now. I uninstalled the last Atlas CTP and installed the new AJAX. I also installed the new Toolkit and added a reference to it, and added the controls to the toolbox, but I'm still getting errors on my page. I change my Reference directive to match the new AJAX and updated all the control extenders to say ajax instead of atlas. But I'm still getting errors, especially with control toolkit properties.

Is there a better explanation on updating everything? I'm assuming all my AJAX updated, but the toolkit seems to giving me problems.

Thanks for all the help thus far!!


You may be experiencing some of the same issues some folks have already brought up... however without specific error messages kinda hard to guess what ypou are experiencing...

In terms of the toolkit the biggest item is the fact that the 'extender' controls are now part of the actual control properties. One idea to try is compare what feature you are implementing with how the asp.net code looks like in the example website pages of the toolkit. Additional - the Migration.Doc that is available at the link ref above - will give you some explicit examples on the conversion changes...


ooohhhh so I don't have to setup the properties for the extenders IN the extenders?

I'll look into that.

Thanks!


ok I'm sure the AJAX portion of my project is updated successfully.

I'm still having alot of problems with my control Toolkit. The only controls I have in my project are Accordians. When I load the page I get this error:

Parser Error

Description:An error occurred during the parsingof a resource required to service this request. Please review the followingspecific parse error details and modify your source file appropriately.

Parser Error Message:Type'AjaxControlToolkit.Accordion' does not have a public property named'AccordionPane'.

Source Error:

 
Line 260:                                                     ContentCssClass="accordianContent" FadeTransitions="true" 
Line 261:                                                     FramesPerSecond="40" TransitionDuration="250" AutoSize="Limit">
Line 262:            <ajaxToolkit:AccordionPane ID="AccordionPane1" runat="server" ContentCssClass="accordianContent" HeaderCssClass="accordianHeader">
Line 263:                <Header>
Line 264:??????????????? <a href\u003d"" onclick\u003d"return false;" class\u003d"accordianLink"> Communication </a>
\n \n\n\n


\nSource File:/bptWeb/ContactsDetail.aspx ?? Line:262

\n\n\n\n\n\n\n\n",0]);D(["ce"]);//-->Line 264: <a href="http://links.10026.com/?link=" onclick="return false;" class="accordianLink"> Communication </a>
 
I successfully changed my directives and manually updated my web.config like the migration.doc says and I've rebuilt the project, but I still get these problems with the Accordians.
Any ideas? Thanks for the help! 


Are you doing anything with code-behind that used to reference the extender properties? From the snippett above I can't see anything wrong - but if you still have codebehind that references the old extender method then I would assume it would generate an error as such what you are seeing...

Ok I followed the instructions about updating the scriptmanager, but its still giving the error

"Element 'ScriptManager' is not a known element. This can occur if there is a complication error in the website"
Here's what the scriptmanager tag looks like:

<asp:ScriptManager ID="sm1" runat="server" /
I get the same errors for my AccordianPane controls that are referenced in the above post.

I also noticed in the Migration guide it says:


Deletethe old version of Microsoft.Web.dll from the bin directory of yourapplication.

But I didn't have one, I hadMicrosoft.Web.Atlas.dll and I renamed the extension to OLD. Here's what I have in my bin folder (it may help):
AjaxControlToolkit.dll
AjaxControlToolkit.pdb
Microsoft.AtlasControlExtender.dll (??)
Microsoft.Web.Atlas.dll.OLD (this is what I renamed according to the instructions in the migration guide.

Thanks for the quick responses and all the help!


Ok I got the accordian pane working, turns out I forgot to add the new <Panes> tag around the AccordianPanes :)

Does my bin folder look ok now though? Do I need to delete everythign referencing 'Atlas'?

Thanks!


Personally I find having the old dlls in the bin can be a bad thing. Unless you do a clean solution - sometimes that caching of the dll makes things unpredicatble. I move the old dlls out to another folder and after cleaning up all the references and such - then recompile. If you still need to play around with the older Atlas bits - merely just make a copy of your solution and you can play with both without either disrupting the other... It makes it cleaner and you know what you are dealing with..


Great! I'm going to delete them unless you guys say otherwise. I don't plan on going back to Atlas CTP at all.

Thanks!

Saturday, March 24, 2012

Conditional xml-script

I working with Beta 2 and CTP for November, I'd like to make a drop down that when it changes if the value isn't US then it changes a label to be Province instead of the default state. Can someone please help me?OK, so this post has been open for several days, is there seriously no one in this community who can tell me how to get xml-script working with a simple example? All I want to be able to do is use xml-script to bind two controls together so that if the country drop-down is changed to something besides country it changes the text property of a label or the innerhtml of a div to province instead of state. I didn't think this one would sit so long with no reply... Am I just missing the tutorial or quickstart where this is explained? Thanks for any help you can offer.

Wednesday, March 21, 2012

ComponentArt 2006.1 and Atlas

I was testing the ComponentArt menu control with a site that has March CTP Atlas installed. I am seeing some very strange behavior. I originally tested the menu control with a single page and no Atlas stuff enabled. It worked as expected. Then I put the menu control into a master page with

<atlas:ScriptManagerID="SM1"runat="server"EnablePartialRendering="true"/>

Now the functionality of the menu and the updatepanel contents is at best inconsistent. Within a single updatepanel located on a content page I have a dropdownlist that has an event and a submit button that has an event. Neither event fires. If I remove the menu control, all works correctly again.

When both the menu control and scriptmanager are in the master page, even pages that don't have any atlas functionality don't work correctly. If I remote the scriptmanager, these other pages work successfully.

I am suspicious that these two items, ComponentArt and Atlas, are beating against each other for AJAX type functionality. Has anyone else had any success using both of these together?

Thanks, Mike

I had the same problem with the same setup, Master Page, Component Art 2006.1 Menu, where all worked fine on localhost, then strange problems you describe showed up on the live site.

The problems were event different when using different browsers. I am back to Feb CTP of Atlas.


I take it from the fact that you are back to using the Feb CTP, that the issue does not appear with it.

I wonder if the Atlas team is looking into this. I hate to start using these two together and find out that the release version of Atlas still has the issue with ComponentArt. By the way I test Telerik's menu control and it did not show the same issue. So it must be something specific between these two.

Thanks,

Mike

Compilation Error

All

after removed CTP July and install new AJAX Beta and updated all aspx to the new sintax.

No error found by vs2005 but when I run my aspx page I get this ambiguous message.

I tried to remove all link and files in temporary folder referrer to ATLAS but it still here again!

Any suggest?

Thanks

Compiler Error Message:BC30560: 'ScriptManager' is ambiguous in the namespace 'Microsoft.Web.UI'.

Line 31: <uc1:WUC_title ID="WUC_title1" runat="server"></uc1:WUC_title>
Line 32: <form id="form1" runat="server">
Line 33: <asp:ScriptManager ID="ScriptManager1" runat="server">
Line 34: </asp:ScriptManager>
Line 35:


c:\winnt\system32\inetsrv> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\vbc.exe" /t:library /utf8output /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\d547c714\d7a9717d_d180c601\OND_ClassLibrary.DLL" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\2368b467\b69d089f_af90c201\mmsseclib.DLL" /R:"C:\WINNT\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll" /R:"C:\WINNT\assembly\GAC_MSIL\System.Design\2.0.0.0__b03f5f7f11d50a3a\System.Design.dll" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\5669f663\00e1cd96_c9afc601\Microsoft.Web.Atlas.DLL" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\6ecfa066\00012fae_52cbc501\FredCK.FCKeditorV2.DLL" /R:"C:\WINNT\assembly\GAC_MSIL\Microsoft.Web.Extensions\1.0.61025.0__31bf3856ad364e35\Microsoft.Web.Extensions.dll" /R:"C:\WINNT\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll" /R:"C:\WINNT\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\11824672\00fbf278_c3f3c601\AjaxControlToolkit.DLL" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_bes0lfzq.dll" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\957d672b\00b4c475_2f69c201\Interop.CAPICOM.DLL" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Code.a4qzeis7.dll" /R:"C:\WINNT\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll" /R:"C:\WINNT\assembly\GAC_MSIL\System.Web.Mobile\2.0.0.0__b03f5f7f11d50a3a\System.Web.Mobile.dll" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\987a2f72\ce3d2c67_e7f6c601\DAR.DLL" /R:"C:\WINNT\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll" /R:"C:\WINNT\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll" /R:"C:\WINNT\assembly\GAC_MSIL\System.Web.Services\2.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll" /R:"C:\WINNT\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\d5f0dc14\007a9e01_71adc501\Calendar.DLL" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_zclqj-6t.dll" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\assembly\dl3\2d8d3127\00cbc46a_b5b4c601\Microsoft.AtlasControlExtender.DLL" /R:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_g0xxdjzm.dll" /out:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_7alj5o6n.dll" /D:DEBUG=1 /debug+ /win32resource:"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\7alj5o6n.res" /define:_MYTYPE=\"Web\" /imports:Microsoft.VisualBasic,System,System.Collections,System.Collections.Specialized,System.Configuration,System.Text,System.Text.RegularExpressions,System.Web,System.Web.Caching,System.Web.SessionState,System.Web.Security,System.Web.Profile,System.Web.UI,System.Web.UI.WebControls,System.Web.UI.WebControls.WebParts,System.Web.UI.HtmlControls "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_7alj5o6n.0.vb" "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_7alj5o6n.1.vb"

Microsoft (R) Visual Basic Compiler version 8.0.50727.42
for Microsoft (R) .NET Framework version 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.

C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_7alj5o6n.0.vb(264) : error BC30560: 'ScriptManager' is ambiguous in the namespace 'Microsoft.Web.UI'.

Private Function __BuildControlScriptManager1() As Global.Microsoft.Web.UI.ScriptManager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_7alj5o6n.0.vb(265) : error BC30560: 'ScriptManager' is ambiguous in the namespace 'Microsoft.Web.UI'.

Dim __ctrl As Global.Microsoft.Web.UI.ScriptManager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dar\202d0bcf\2e13232b\App_Web_7alj5o6n.0.vb(1126) : error BC30560: 'ScriptManager' is ambiguous in the namespace 'Microsoft.Web.UI'.

Dim __ctrl1 As Global.Microsoft.Web.UI.ScriptManager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
c:\inetpub\wwwroot\dar\Default.aspx(33) : error BC30560: 'ScriptManager' is ambiguous in the namespace 'Microsoft.Web.UI'.

__ctrl = New Global.Microsoft.Web.UI.ScriptManager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

You probably still have a remnant of the Atlas namespace, which would be different but would share class and method names.

Check that you have removed ALL instances to the Microsoft.Atlas.dll. Ensure you've uninstalled it, deleted from any "bin" folders and removed the reference.