Showing posts with label beta. Show all posts
Showing posts with label beta. Show all posts

Wednesday, March 28, 2012

Virtual Earth v4/ASP.NET AJAX v1.0 Beta 2 Bug

Hi All,

I ran into a bug with the Virtual Earth v4/ASP.NET AJAX v1.0 Beta 2 combination in which I receive the following error:

Sys.InvalidOperationException: Object Microsoft already exists and is not a namespace.

The following is a simple reproducible case. I would really appreciate it if someone from Microsoft could confirm that they are aware of this bug and provide status.

I have also posted this message in the Virtual Earth forum in reply to SpeedOfSPin's post(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=897625&SiteID=1) regarding this bug as I am not sure in which team's product the issue resides.

This is not an issue if I revert back to using Virtual Earth v3 but obviously I would prefer to be able to make use of v4.

1<%@dotnet.itags.org. Page Language="C#" %>23<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
45<script runat="server">
67</script>
89<html xmlns="http://www.w3.org/1999/xhtml">
10<head id="Head1" runat="server">
11 <title>Virtual Earth v4/ASP.NET AJAX v1.0 Beta 2 Bug</title>
12 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
1314 <script type="text/javascript" src="http://dev.virtualearth.net/mapcontrol/v4/mapcontrol.js"></script>
1516 <script type="text/javascript">
17 function pageLoad()
18 {
19 var map = new VEMap('map');
20 map.LoadMap();
21 }
22 </script>
2324</head>
25<body>
26 <form id="form1" runat="server">
27 <asp:ScriptManager ID="ScriptManager1" runat="server">
28 </asp:ScriptManager>
29 <div id="map" style="position: relative">
30 </div>
31 </form>
32</body>
33</html>
34
Thanks a lot,I'm also having this issue. Has anyone found a work around?
Anyone? MSFT?

I'm struggling with this as well. Here's another thread regarding the issue:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=897625&SiteID=1

I hope this gets resolved soon.


Monday, March 26, 2012

VS 2005/MS Ajax Beta Application no longer runs on Live server but does in Dev. Help!

I have just migrated from Atlas to MS Ajax Beta and after a lot of hassle to get the application working I decided to publish to our test web server. When I go to the URL for our test server all I get is a blank page but the IE progress bar (the bar at the bottom that show the page loading status) just flickers like crazy. It works fine on my dev machine but as soon as I publish it, no joy!

I really need some help on this as I don't really have a clue and I don't really fancy having to roll back to Atlas just to get this to work live.

Cheers,

FF

Ignore me, I'm stupid!!

I hadn't checked if the extensions were installed on the server!! DOH!!!


hello.

well, you must install ajax extensions on the live server and configure your site to use asp.net 2.0. have you done that already?

VS cant recognize all tags from AJAX framework.

For some reason starting from Beta VS marks all tags that represent AJAX makeup as invalid even though page compiles and runs OK.

Did anybody see this?
Thanks

there's already 4 or 5 topics on this... here's one of them (http://forums.asp.net/thread/1435993.aspx)

Wednesday, March 21, 2012

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 Parts and Atlas with Beta 1

Could someone please help me with the steps required to get asynchronous drag-and-drop of Web Parts using Atlas Beta 1?

I have my own web part manager that inherits fromWebPartManager. Do I need to explicitly make it inherit from the Atlas web part manager instead? The online pre-Beta 1 tutorials on this topic (which I never got to work after several days of trying) said to add a <tagMapping> for the Atlas WebPartManager and WebPartZone. Is this still required?

I'm also using master pages and want the ScriptManager and WebPartManager to both live on the master page. Is this OK? Would there need to be an update panel in the master page since the whole content area will need an asynch refresh with web parts in the picture?

This topic seems like it would be a common question to me, so I hope someone will explain the "approved way" of combining the two.

Thank you,

Terry

I haven't read yet a successful experience with Webparts and beta1, that's why I am waiting for a future release, so I can migrate from the July CTP.


It would be nice if someone from Microsoft could respond.

I'm replying once again to move this issue to the top of the forum.

Can't someone on the Atlas team help me with this? I've seen other posts on the same topic, so I know I'm not the only one that can't this to work.

Web service and time zones problem in AJAX ASP.NET Beta 1.0

Hello, I have the followong exception, during requesting a webservice.

Requested URL:https://www.some_site.com/Services/Logout.asmx/js
Exception Message: Specified argument was out of the range of valid values.
Parameter name: utcDate
Exception Details: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: utcDate
at System.Web.HttpCachePolicy.UtcSetLastModified(DateTime utcDate)
at System.Web.HttpCachePolicy.SetLastModified(DateTime date)
at Microsoft.Web.Script.Services.RestClientProxyHandler.ProcessRequest(HttpContext context)
at Microsoft.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Thread: IsImpersonating = False

As I investigated, the problem originates because utcDate in method UtcSetLastModified is the date in future. This happens because the time zone on our side differs from the server's time zone where we deploy our application.

Please, HELP!

Thanks for letting us know about this problem! This looks like a valid bug.

How are you deploying your app? Am I correct in guessing you are using the "Publish web site" feature of VS or the "aspnet_compiler"? If not, can you please let me know how you deploy it?

Do you mean that the time zone is different on the computer where you built your app and the server where you deploy?

Until we fix the bug, one workaround I can think of is to "touch" the precompiled dlls in our app's bin directory to update the last modfied time on them.


We build our application using MSBuild on local TFS (one time zone), and then just copy all builded dll's and other files to production server (it is in another time zone).

Another workaround i've found is to set in ScriptManager->ServiceRefrence InlineScript property to true, then all js for my web service will be included in the output page, so there's no need to requesthttps://www.some_site.com/Services/Logout.asmx/js