Visual Studio 2008 And AJAX Framework 3.5 - Control KIT

Hi friends ...

I need heap of helps on AJAX Framwork 3.5.
I just Installed Visual Studio 2008 and AJAX Control ToolKit for Ms Framework 3.5 - 11119

I've got Error Message (below) when i create Accordion AJAX Control Kit.

Error 1 The type or namespace name 'AjaxControlToolkit' could not be found in the global namespace (are you missing an assembly reference?)

I've included the AjaxControlKit.dll in my Bin folder. I've added the <%@dotnet.itags.org. Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
at the top of the page. i've created the Ajax Control Kit. but still facing this problem.

I've got a warning : Generation of designer file failed, unknown tag ... on my textboxWatermarkextender. but strangely when i run the project, the target textbox runs properly.

anyone have any experienced ?

By the way, for moderator :)

Last week, i forgot my password to log in to this forum, i clicked the "forgotten password" link ... as it asks me to enter my email address when i register for this forum.
i put in my email address , and request for a new password.

When the email confirmation arrived in my inbox, i clicked the formatted link as instructed in the email, but when it always say ... " You dont have permission to do the task " ... MsgID = 31 ...
i tried many times and came with no result. Fortunately as 10 days past by, suddenly i remember my password ...

how it could be happening? and what to do next if i forgot my password ? :)

thanks ...

Hi On3_Cool,

on3_cool:

I need heap of helps on AJAX Framwork 3.5.
I just Installed Visual Studio 2008 and AJAX Control ToolKit for Ms Framework 3.5 - 11119

I've got Error Message (below) when i create Accordion AJAX Control Kit.

Error 1 The type or namespace name 'AjaxControlToolkit' could not be found in the global namespace (are you missing an assembly reference?)

I've included the AjaxControlKit.dll in my Bin folder. I've added the <%@. Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
at the top of the page. i've created the Ajax Control Kit. but still facing this problem.

I've got a warning : Generation of designer file failed, unknown tag ... on my textboxWatermarkextender. but strangely when i run the project, the target textbox runs properly.

anyone have any experienced ?

It is recommended to add reference to the AjaxControlToolkit.dll(right click on the bin directory, and choose "Add Reference"), and then AjaxControlToolkit.dll will be added to the bin directory automatically.

Also you can register AjaxControlToolkit on the web.config. You can use template to create an Ajax Control Toolkit enabled website.

For your second question, please send private messages to the website moderators. Thanks for understanding.

If you have more questions , please feel free to let me know.

Best regards,

Jonathan

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)

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.