Deployment Problem

Recently I developed a website and used atlas for paging gridviews and some other things, all work correctly on my local host. But when I uploaded it to the host(the host supports asp.net 2.0), It doesnt work, I dont recieve any error but there is nothing like atlas there! I uploaded the dll as well as the correct configuration in web.config.

Is there anything else to do? Do you guys have any idea?

hello.

1. check if the application is configured to use asp.net 2.0

2. use fiddler to see what happens during a partial postback. it should give you some clues on what's going on,

The app uses asp.net 2.0, I have used so many features of asp.net 2.0 succesfully there. But the only problem is it do not refereshesh partially, it refereshesh totaly. It works well on local, but doesnt work on the shared host

hello again.

have you tried using fiddler to intercept the http traffic to see what you're getting on the client after a partial postback?

Hi...i'd the same problem...

Do you have URLSCAN or another security software installed in the server?

You need configure this software for allow requests with extesion .axd.

Sorry my bad english...

About URL Scan stuff, I should ask the guys in the hosting provider company, because this is a shared hosting plan, and about the fiddler no, I have not tested yet.
I used fiddler now, first when the page is loaded, for atlas .axd scripts it shows 404 error. When the partial postback is fired, it doesnt referesh all requestst but again it cannot find the scripts. If you want to take a view go tohttp://www.shokri.net/ I guess I should copy the javascript files. Do you have any idea?
With certainty, this is a problem of configuration in server. In my case, the URLSCAN blocked all attempts for any .axd scripts generating error 404.
Something more funny, On this host I cant use FreeTextBox WYSIWYG the way Ive always used, and the error comes from handlers again.
The guys from hosting compay say they have a url scan, now what is your suggestion?
They need configured the file urlscan.ini to allow request .axd extension. After, they need restart IIS.

Yeah I asked them to. Honesty for .axd file url protection is not usable, because these .axd files do not often have something secure within.