Karatas, FERHAT
I would love to change the world, but they won't give me the source code!
30.8.2009 16:43:40 - Filed under : C# | Asp.net | CSS | AJAX
Implementing the HTTP header is beneficial if a site owner wants most of their site to render as it did in IE7 or if there are no plans to update site content. Inclusion of this header honors any Quirks mode pages that belong to the site. Use below statement at top of your page :
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
or use it in web.config :
            <add name="X-UA-Compatible" value="IE=EmulateIE7" />
Using the meta-tag on a per-page basis is beneficial when the publisher wants to opt-in specific pages to render as they did in IE7.

NOTE: The X-UA-Compatible tag and header override any existing DOCTYPE. Also, the mode specified by the page takes precedent over the HTTP header. For example, you could add the EmulateIE7 HTTP header to a site, and set specific pages to display in IE8 mode (by using the meta-tag with content=”IE8”).

Using the IE=EmulateIE7 compatibility tag is a simple way for users to continue their current experience when browsing your site until you can update with more standards-compliant content.  Although adding this tag will prevent most display issues, you may also need to update your site to properly detect IE8.

Keywords : Emulate IE7
with 0 comments

'System.web.extensions' is already defined.
8.2.2009 20:28:33 - Filed under : Asp.net | AJAX
Error : Section or group name 'system.web.extensions' is already defined. Updates to this may only occur at the configuration level where it is defined.

I have a web application project which developed under 3.5 .net framework. Also there is a virtual directory under the project that developed in previous framework. These two sections belongs to their web.config file.

Root Project’s config : <sectionGroup name="system.web.extensions" type= "System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

Virtual Directory’s config : <sectionGroup name="system.web.extensions" type= "System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

Solution : <configuration> <configSections> <sectionGroup name="system.web.extensions2"… I  changed the “name” attribute of the sectionGroup of the Virtual Directory. Site and everything seems to be working now.

Keywords : sectionGroup inheritance issue, ajax migration, system.web.extension.

with 0 comments

Ajax Control Toolkit-Framework3.5 SP1 - Version 3.
28.9.2008 14:26:58 - Filed under : Asp.net | AJAX
Release Notes - Version 3.0.20820
2008-08-20 release of the AJAX Control Toolkit targets the official release of .NET Framework 3.5 SP1 and Visual Studio 2008 SP1.

To download :

How To Implement :
  • Download source version. (AjaxControlToolkit-Framework3.5SP1.zip)
  • Extract it to C:\Program Files\Ajax Control Toolkit (create directory)
  • Copy content of C:\Program Files\Ajax Control Toolkit\SampleWebSite\Bin to C:\Program Files\Ajax Control Toolkit\Binaries
  • In VS2008 toolbox. Add tab - Choose items
  • Select C:\Program Files\Ajax Control Toolkit\Binaries\AjaxControlToolkit.dll

Keywords : Ajax Toolkit 3.0, Updates for .NET Framework 3.5 SP1 and Visual Studio 2008 SP1
with 0 comments

AJAX Control Toolkit - Setup your environment
4.8.2007 18:49:25 - Filed under : AJAX
Install binaries
  1. Install the latest ASP.NET AJAX Extensions 1.0 package
  2. Unpack the AJAX Control Toolkit into a folder on your computer
Configure Visual Studio 2005 or Visual Web Developer
  1. Create a new web site from the ASP.NET AJAX web site template by opening the "File" menu, clicking "New", "Web Site...", and picking "ASP.NET AJAX Web Site" under "My Templates"
  2. Right-click on the Toolbox and select "Add Tab", and add a tab called "AJAX Control Toolkit"
  3. Inside that tab, right-click on the Toolbox and select "Choose Items..."
  4. When the "Choose Toolbox Items" dialog appears, click the "Browse..." button. Navigate to the folder where you installed the ASP.NET AJAX Control Toolkit package. You will find a folder called "SampleWebSite", and under that another folder called "bin". Inside that folder, select "AjaxControlToolkit.dll" and click OK. Click OK again to close the Choose Items Dialog.
  5. You can now use the included sample controls in your web sites!
Note 1 : Add 3 dll to your reference from "C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025". And set it's "Copy Local" property to "True". These operation provide you to add related dll to bin directory instead of using GAC.
Havent you seen "Copy Local" property ? May be you do not know "Web Application Project". Web Application Project Model is a new web project option for Visual Studio 2005 that provides the same conceptual web project approach as VS 2003 (a project file based structure where all code in the project is compiled into a single assembly) but with all the new features of VS 2005 (refactoring, class diagrams, test development, generics, etc) and ASP.NET 2.0 (master pages, data controls, membership/login, role management, Web Parts, personalization, site navigation, themes, etc).

Note 2 : You should have these record at web.config
      <add verb="GET,HEAD" path="ScriptResource.axd"
type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"/>

Keywords : AJAX Control Toolkit setup, AJAXExtensionsToolbox.dll, System.Web.Extensions.Design.dll, System.Web.Extensions.dll
with 0 comments

Element “ScriptManager” is not a known element.
13.2.2007 11:45:34 - Filed under : AJAX
If you moved from Ajax Beta2 to RC1 you might encounter that kind of problem, all other controls are affected as well like Element ‘UpdatePanel’ is not a known element.
Element “ScriptManager” is not a known element. This can occur if there is a compilation error in the website.

Your form.designer.cs is no longer code generating anything, and you are using a master page – then you can probably fix it by doing the following:

  1. Open your master page in the designer by double clicking it in visual studio.
  2. Open your suspect .aspx file
  3. Right click on the toolbox in visual studio and click 'Reset Toolbox'
  4. Wait for this to complete
  5. Delete the "script manager" or "update panel" that you dropped before (if it exist)
  6. Switch to "Design Mode", and drop a new script manager from the ajax extensions group onto the page.
  7. Check that your designer is now regenerating code.
  8. And build your project

Hope this helps.

Related Terminology : Asp.net Ajax 1.0 RC1 migration

with 0 comments

Previous | Next
Current Page: 1