Atlas not supported by web host?

it would help if you gave more details, did you deploy the atlas dll?

hello.

can you provide a link to the page? btw, you must make sure that your app is using asp.net 2.0.

I have similar problem. But in my case Autocomplete function works fine on my PC, but when I upload it on server... nothing hapens...

I thing that is some security problems on using web service! Web services work fine when I don`t use Atlas...

here is link:
http://mailer.prozorama.com
webservice I`m using for AutoComplete is http://mailer.prozorama.com/PhoneBook.asmx and I can`t access it because some security reasons...

It is just a test page for my PhoneBook... Any help would be fine...

Does Hosting Provider need to be configured for using Atlas Aplications?
Thnx... Zrinko

Sorry, I was a little frustrated by the time I got to writing that. There are two pages currently uploaded. Yes, the atlas.dll is in the application's /bin directory.

http://www.velocitydatasolutions.com/sandbox/Wiki/ is one of them, it worked fine for the drag and drop of the colored div on my dev box, but does not on the host.

http://www.velocitydatasolutions.com/sandbox/Wiki/Declarative.aspx is the other. It's a test of using the declarative markup for binding a web service (web service is housed in the same application path as the page asking for it).

Both of these examples are straight from the tutorials on here, I wa sactually just uploading them for my friend to check out.

Just noticed I didn't respond to the other question. The appis using .Net 2.0.

hello.

it looks like one cannot open the webservice from the browser. can we use get to obtain the web service or have you disabled it on the site?

it wasn't just the web service thing, it was any Atlas functionality, and I *just* figured out the problem.

Not sure if this was my misunderstanding, but I *thought* that starting with one of the atlas project templates would be good enough. For on my local box it is. For those playing from home the atlas template puts the atlas.dll file in the /bin, modifies your web.config to include a bunch of new sections and references to key things, and puts in some atlas markup into the default.aspx page that it starts with.

What I finally did to solve the problem (and it seems to work with drag and drop and web services, at least, haven't tried more than that) is make a directory to hold all the .js files that came with the atlas download, and then I had to make explicit includes of them in the page that needed them, old-style (e.g. <script type="text/javascript" src="http://pics.10026.com/?src=Scripts/atlas.js"></script>). Once I did that (and I had to include the atlasUIDragDrop.js the same way), it all worked.

Now, my gut says this isn't how it should work in the release version of atlas whenever that occurs, but at least I can make stuff move now.

Thanks for your time and support

Paul

hello.

well, then this must be related with the way your web app is configured. btw, if ou look at the source of your page you should see several webreosurce.axd entries set as the source property of script blocks. these items should include the client files on the page; if they aren't doing that then you probably haven't configured the web app properly...

Ok, I assume you're talking about the web.config and in this case I just took the default one that installs with the template. Can you tell me what I have to do differently? current web.config is copied/pasted below (I removed (just now) the long blocks of comments that come with the default web.config).

The pages did render those webresource.axd entries that you're referring to, and still do. But if I pull out my manually added <script> includes the atlas functionality goes away.

<?

xmlversion="1.0"?>

<

configuration>

<!--

The configSections define a section for ASP.NET Atlas.

-->

<

configSections>

<

sectionGroupname="microsoft.web"type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup">

<

sectionname="converters"type="Microsoft.Web.Configuration.ConvertersSection"requirePermission="false" />

<

sectionname="webServices"type="Microsoft.Web.Configuration.WebServicesSection"requirePermission="false" />

<

sectionname="authenticationService"type="Microsoft.Web.Configuration.AuthenticationServiceSection"requirePermission="false" />

<

sectionname="profileService"type="Microsoft.Web.Configuration.ProfileServiceSection"requirePermission="false" />

</

sectionGroup>

</

configSections>

<!--

The microsoft.web section defines items required for the Atlas framework.

-->

<

microsoft.web>

<

converters>

<

addtype="Microsoft.Web.Script.Serialization.Converters.DataSetConverter"/>

<

addtype="Microsoft.Web.Script.Serialization.Converters.DataRowConverter"/>

<

addtype="Microsoft.Web.Script.Serialization.Converters.DataTableConverter"/>

</

converters>

<

webServicesenableBrowserAccess="true" />

<!--

Uncomment this line to enable the authentication service.

<authenticationService enabled="true" />

-->

</

microsoft.web>

<

appSettings/>

<

connectionStrings/>

<

system.web>

<

pages>

<

controls>

<

addnamespace="Microsoft.Web.UI"assembly="Microsoft.Web.Atlas"tagPrefix="atlas"/>

<

addnamespace="Microsoft.Web.UI.Controls"assembly="Microsoft.Web.Atlas"tagPrefix="atlas"/>

</

controls>

</

pages>

<

compilationdebug="false">

<

buildProviders>

<

addextension=".asbx"type="Microsoft.Web.Services.BridgeBuildProvider" />

</

buildProviders>

</

compilation>

<!--

ASMX is mapped to a new handler so that proxy javascripts can also be served.

-->

<

httpHandlers>

<

removeverb="*"path="*.asmx"/>

<

addverb="*"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.

-->

<

addverb="*"path="atlasbatchcall.axd"type="Microsoft.Web.Services.MultiRequestHandler"validate="false"/>

<

addverb="*"path="atlasglob.axd"type="Microsoft.Web.Globalization.GlobalizationHandler"validate="false"/>

<

addverb="*"path="*.asbx"type="Microsoft.Web.Services.ScriptHandlerFactory"validate="false"/>

</

httpHandlers>

<

httpModules>

<

addname="ScriptModule"type="Microsoft.Web.Services.ScriptModule"/>

<

addname="BridgeModule"type="Microsoft.Web.Services.BridgeModule"/>

<

addname="WebResourceCompression"type="Microsoft.Web.Services.WebResourceCompressionModule"/>

</

httpModules>

</

system.web>

</

configuration>

hello again.

well, in fact i was talking about the IIS configuration. how is it set up? if you use iis admin console, you'll be able to see if your app is configured to use asp.net 1.1 or 2.0...

As I previously stated, I don't own the server, it's a GoDaddy.com server, and I don't have access to the IIS. Having said that, it *IS* set up as an ASP.net 2.0 application, and I've been running the site for quite some time now using .Net 2.0 features (objectdatasource, gridview, providers, Master pages, etc). I haven't had any issues with any custom controls I've built or any .Net 2.0 feature that I've tried.

hello again.

well, what can i say...not getting the files sent through webresource.axd is sign of not using 2.0...on the other hand, i'm not a system admin...well, i'm glad it's working now...

Well, thanks for your time and skull-sweat, anyway. The interesting thing (to me) is that the site makes use of the asp:menu control (among others) which, according to the documentation, use webresource.axd to serve up client script as well. You'd think that if the webresource.axd isn't functioning properly due to some site misconfiguration, that those wouldn't work either...

Ok, so the last question I asked tickled my brain a little. Here's the setup.

Main site (has all my content, etc, including the above-referenced menu control, etc).

the sandbox/wiki site I made into its own application root and was using it to test the atlas stuff, but I verified (as I said above) that it was in fact using .Net 2.0 as well. what I'd forgotten was that when I first started using the asp:menu control on themain site, a year+ ago, it didn't work. It didnt' work until I made a file in the root that had no content called WebResource.axd. I stumbled on that answer back then when trolling the forums after scratching my head for a while. I still don't know why it works (webresource, iirc, is not supposed to be a 'real' file) but it does. I took out my manual <script> tags and added the blank webresource.axd file and it's working wonderfully...

Once again, thanks for the help.

Paul