viewing the script source

Previously, the script source was in a ScriptLibrary directory in a web
application. I want to view the source now with the March CTP. Is there a
way to view the source in the clientside javascript now?

Wally

--
Wallace B. McClure
"The Harder I Work, the Luckier I Get."
Listen to "The ASP.NET Podcast" at http://www.aspnetpodcast.com/
Database Award: http://url123.com/vc3er
Microsoft MVP - Visual Developer ASP/ASP.NET
AspInsider
"AJAX for ASP.NET" Coming Soon!
ADO.NET Book: http://url123.com/vc2bu
865-693-3004
118 Durwood Rd.
Knoxville, TN 37922
http://www.scalabledevelopment.com/
Blog: http://weblogs.asp.net/wallym/

Wally, the atlas scripts as now packaged as resources in the atlas dll. The Atlas MSI setup also installs them in the c:\Program Files\Microsoft ASP.NET\Atlas\v2.0.50727\Atlas\ScriptLibrary\Debug\ directory for you to view.

enjoy
-jhawk

Virtual Earth: Mapstyle - oblique Question

It seems like March CTP doesn't includue Mapstyle - Oblique. Is that ture?

Correct, the Atlas March CTP does not support the Oblique feature of Virtual Earth.

Visible attribute on Atlas controls

Hi,

This small piece of code doesn't work in the current Atlas CTP:

<div>

<atlas:ScriptManagerID="ScriptManager1"runat="server"EnablePartialRendering="True">

</atlas:ScriptManager>

</div>

<atlas:UpdateProgressID="UpdateProgress1"runat="server"Visible="false">

<ProgressTemplate>

Contacting server...

<br/>

<br/>

<inputid="abortButton"runat="server"type="button"value="Abort Request"/>

</ProgressTemplate>

</atlas:UpdateProgress>

The controls that implement the IScriptObject (UpdateProgress,…) use to override the RenderScript method in order to write xml/script output. The problem arrives when visible="false" for this control; then the control itself doesn't render, but it does the xml/script, what provokes a javascript error. This behavior is by design? Am I correct? Then, how could I override this behavior (and avoid this problem)? One solution could be to unregister the control in the script manager, but there is no ScriptManager.UnregisterControl (control).

Thanks

Fran

Anybody there??

style="display:none;"

Type 'Microsoft.Web.UI.UpdateProgress' does not have a public property named 'Style'

I think it would be great to have a nice Style or CssClass property, but there is nothing like that at the moment.

but that gave me another idea: a div surrounding the updateprogress, and apply the style to the div. it is not really a nice solution, but it works.

thanks

Fran

visual web developer 2005 express

Hi,

will the sample control toolkit work in visual web develoer? i installed the ajax .net rc1, control sample web site, latest ctp. When i open and run the sample project, it shows no error and displays the controls. but, the none of the controls is working.

thanks

it will work under visual web developer

do you see any javascript error?

No. there is no compilation, runtime or javascript error. But, it the sample controls still not working

thanks

VS 2005 & Atlas Problem

I recently had to reinstall my OS. I reinstalled VS 2005 & Atlas April CTP, however when I try and use VS.net to edit the refrences or components sections (shown below) the smart logic for all the methods & functions dosent work.Has anyone else had this problem?

<scripttype="text/xml-script">

<page xmlns:script=

"http://schemas.microsoft.com/xml-script/2005">

<references>

</references>

<components>

</components>

</page>

</script>Hi,

there's no intellisense support at the moment for the Atlas declarative script.

WCF problem with June CTP on WinFX Beta 2

The documentation states that "The WCF support in this version of "Atlas" requires Beta 2 of .NET Framework version 3.0."

Unfortunately, when I run the wcf_cs/Simple.aspx from the Atlas Documentation website (run as a filesystem) on Beta 2 (on XP SP2), I get the following stack trace:

[InvalidCastException: Unable to cast object of type 'System.Web.Compilation.BuildResultCustomString' to type 'System.Web.Util.ITypedWebObjectFactory'.] System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +161 System.Web.Compilation.BuildManager.GetCompiledType(VirtualPath virtualPath) +36 System.Web.Compilation.BuildManager.GetCompiledType(String virtualPath) +81 Microsoft.Web.Services.WebServiceData.GetWebServiceData(String virtualPath, Boolean failIfNoData) +271 Microsoft.Web.Services.WebServiceData.GetWebServiceData(String virtualPath) +30 Microsoft.Web.UI.ScriptManager.BuildScriptElement(String servicePath) +399 Microsoft.Web.UI.ScriptManager.GetScriptReferences() +979 Microsoft.Web.UI.ScriptManager.RenderXmlScript(TextWriter writer) +110 Microsoft.Web.UI.ScriptManager.OnPagePreRenderComplete(Object sender, EventArgs e) +663 System.EventHandler.Invoke(Object sender, EventArgs e) +0 System.Web.UI.Page.OnPreRenderComplete(EventArgs e) +96 System.Web.UI.Page.PerformPreRenderComplete() +32 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4796

Is there anyway to fix or workaround the above problem? Is there a configuration in which WCF will work with ATLAS?

Thanks, Jack

I was able to get the simple service WCF sample to work by pulling the relevant files out into a newly created Atlas enabled test website. I then quickly discovered that navigating (instead of trying to directly view or set simple.aspx as the start page in VS) to the simple service form in the Atlas Documentation website also worked. I'm not sure why -- I nested the service files in my test website and was still able to view it directly. As time permits, I'll see if I can find a cause.

At any rate, WCF appears (I've only tried the samles) to work with the June CTP of Atlas on WinFX Beta 2.

Web Part PartChromeType.None Causes Zone_ToggleDropCues Function Problem

Using the Atlas March CTP, I receive an error using it's webpart stuff.

It is in "function Zone_ToggleDropCues(show, index, ignoreOutline)"

this.initialize = function() {
Sys.UI.Controls.WebParts.WebPart.callBaseMethod(this, "initialize");

_titleElement.detachEvent("onmousedown", WebPart_OnMouseDown);
this.element.detachEvent("ondragstart", WebPart_OnDragStart);
this.element.detachEvent("ondrag", WebPart_OnDrag);
this.element.detachEvent("ondragend", WebPart_OnDragEnd);

if (_zone.get_webPartManager().get_allowPageDesign() && _zone.get_allowLayoutChange()) {
_titleElement.attachEvent("onmousedown", Function.createDelegate(this, mouseDownHandler));
}
}

"_titleElement.detachEvent("onmousedown", WebPart_OnMouseDown);"
says that _titleElement is null.

This happens when I set the chrometype to none for the webpart.

Nathan

We should be handling the case where _titleElement is null. I've filed a bug and this should be fixed in the next release of Atlas. Thanks for reporting it.

-Mike