Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Atlas not working. 1

Status
Not open for further replies.
Apr 11, 2002
193
IN
Hi,

Atlas is not working in my ASP.net website. I created the site as Atlas website.

My web.config file is :

<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<!--
The configSections define a section for ASP.NET Atlas.
-->
<configSections>
<sectionGroup name="microsoft.web" type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup">
<section name="converters" type="Microsoft.Web.Configuration.ConvertersSection" requirePermission="false"/>
<section name="webServices" type="Microsoft.Web.Configuration.WebServicesSection" requirePermission="false"/>
<section name="authenticationService" type="Microsoft.Web.Configuration.AuthenticationServiceSection" requirePermission="false"/>
<section name="profileService" type="Microsoft.Web.Configuration.ProfileServiceSection" requirePermission="false"/>
</sectionGroup>
</configSections>
<!--
The microsoft.web section defines items required for the Atlas framework.
-->
<microsoft.web>
<converters>
<add type="Microsoft.Web.Script.Serialization.Converters.DataSetConverter"/>
<add type="Microsoft.Web.Script.Serialization.Converters.DataRowConverter"/>
<add type="Microsoft.Web.Script.Serialization.Converters.DataTableConverter"/>
</converters>
<webServices enableBrowserAccess="true"/>
<!--
Uncomment this line to enable the authentication service.
<authenticationService enabled="true" />
-->
<!-- Uncomment these lines to enable the profile service. To allow profile properties to be retrieved
and modified in Atlas applications, you need to add each property name to the setProperties and
getProperties attributes. If you intend for all properties to be available, you can use "*"
as a shorthand rather than enumerating each property -->
<!--
<profileService enabled="true"
setProperties="propertyname1;propertyname2"
getProperties="propertyname1;propertyname2" />
-->
</microsoft.web>
<appSettings/>
<connectionStrings/>
<system.web>
<pages>
<controls>
<add namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Atlas" tagPrefix="atlas"/>
<add namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Atlas" tagPrefix="atlas"/>
</controls>
</pages>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="true">
<buildProviders>
<add extension=".asbx" type="Microsoft.Web.Services.BridgeBuildProvider"/>
</buildProviders>
</compilation>
<!--
ASMX is mapped to a new handler so that proxy javascripts can also be served.
-->
<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" type="Microsoft.Web.Services.ScriptHandlerFactory" validate="false"/>
<!--
The MultiRequestHandler enables multiple requests to be handled in one
roundtrip to the server. Its use requires Full Trust.
-->
<add verb="*" path="atlasbatchcall.axd" type="Microsoft.Web.Services.MultiRequestHandler" validate="false"/>
<add verb="*" path="atlasglob.axd" type="Microsoft.Web.Globalization.GlobalizationHandler" validate="false"/>
<!--
The IFrameHandler enables a limited form of cross-domain calls to 'Atlas' web services.
This should only be enabled if you need this functionality and you're willing to expose
the data publicly on the Internet.
To use it, you will also need to add the attribute [WebOperation(true, ResponseFormatMode.Json, true)]
on the methods that you want to be called cross-domain.
This attribute is by default on any DataService's GetData method.

<add verb="*" path="iframecall.axd" type="Microsoft.Web.Services.IFrameHandler" validate="false"/>
-->
<add verb="*" path="*.asbx" type="Microsoft.Web.Services.ScriptHandlerFactory" validate="false"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="Microsoft.Web.Services.ScriptModule"/>
<add name="BridgeModule" type="Microsoft.Web.Services.BridgeModule"/>
<add name="WebResourceCompression" type="Microsoft.Web.Services.WebResourceCompressionModule"/>
</httpModules>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.

<authentication mode="Windows"/>
-->
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm"/>
<error statusCode="404" redirect="FileNotFound.htm"/>
</customErrors>
-->
</system.web>
<!-- Uncomment this if your site globally denies access to anonymous users. The
authentication service and profile service are located under the virtual
"ScriptServices" directory. Since you normally call the authentication web
service with an un-authenticated user, the following location tag can be used
to grant access to anonymous users. If you use anonymous profile support
you will also need to grant access to anonymous users. -->
<!--
<location path="ScriptServices">
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</location>
-->
</configuration>

I am using proper tags in my page. But i dont know why it is not working. Please suggest.

Thanks,
Manish
 
exactly how is it not working. we can't do anything without knowing:
asp.net version (assuming 2.0 since you have AJAX installed)
version of MS AJAX (Atlas was beta/rc; MS AJAX v1.0 is current)
error message
stack trace
relevant code snippets

Jason Meckley
Programmer
Specialty Bakers, Inc.
 
Hi Jason,

Yes, i am using 2.0 and i did download Atlas from

I dont think that it is the correct version for Atlas as i have tried it on various machines and it doesnt work. I was using AJAX 1.0 earlier which did work perfectly, but my client wants Atlas. If you know a correct location from where i can download Atlas then please let me know.

Thanks,
Manish
 
Does your client realize that Atlas was a beta product and is no longer supported?

the link does work. you can only have 1 verson of Atlas/MS AJAX on a given machine. so if you have any version of Atlas or MS AJAX you will have problems installing/using the assemblies.

Atlas has bugs, and major changes occurred within the final months of v1 release. if a system is built around Atlas maintainence will be a nightmare.

Jason Meckley
Programmer
Specialty Bakers, Inc.
 
Thanks Jason for your valuable advice. I had AJAX 1.0 installed before and i had to uninstall it to install Atlas for this project. Do you have a link which mentions that Atlas has problems and AJAX 1.0 should be used instead so that i can convince my client.

Thank you very much.

Manish
 
this document outlines the changes between CTP to RTM. there is not a document that outlines changes from Atlas Beta X to MS AJAX v1 because there were a few MS AJAX RC versons in between.

Jason Meckley
Programmer
Specialty Bakers, Inc.
 
Thanks for your help.

This is enough for the client to get convinced "Applies to:

- ASP.NET AJAX (formerly code-named “Atlas”)"

Highly appreciated.

Manish
 
Hi again. Forgot to ask you one thing. Are there any disadvantages of AJAX 1.0 like performance issues in case of huge applications where there is large amount of data.

Thanks,
Manish
 
the updatepanel is very easy to use, but not effecient. here is the MSDN article for more info. specifically Updates without UpdatePanels.


Jason Meckley
Programmer
Specialty Bakers, Inc.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top