Call a web service

Can somebody explain, is it possible to call a web service which NOT located in the same project as atlas without creating a "bridge"??

Only if that service uses the same virtual directory or *host* location.

So, if the host of the virtual directory or project is:

http://MyHost/..... (where MyHost is your virtual directory/host)

and when you access the service that "host" is not different in anyway, then yes you can. If the host is different or even if there is a port appended to it like:

http://MyHost:1234/... then you will need some sort of bridge.

Note that the example above may work on IE6, but will fail on IE7 and Firefox. This is a limitation of the XMLHttp request object that is the basis for the web service access mechanism.

You could have a different project that exists within a sub-directory of another project which would therefore have the same host name and so would work. But again, if you created a new virtual directory for this sub directory and give it a different host name, then no, it wont work without bridging or writing a custom service to do it for you.

Thx, it was very valuable information.

CalendarExtender makes things slow!

Hello everybody,

I noticed this behavior almost immediately when we used theCalendar Extender for the first time. But I waited to see somebody discussing about it in the forum. It took quite a while...

I have removed all theCalendar Extenders because it slows all the other parts of the ASPX page, for example: when you click on a button to fetch data from the database and load it in a grid, without anyCalendar Extenders its lightening fast... but add aCalendar Extender or 2 and then you can notice it starting to get slow

I have now switched back to the old way, using a Calendar control with aPopupControlExtender to display a pop up calendar, and its fast.
I am using a Master page, themes and my controls are inside anUpdatePanel

I think the usercmarshall26 is also experiencing the same problem which he explains inthis post

(but the Calendar that is displayed using theCalendar Extenderlooks cool!)

Hope somebody can relate to this problem... any suggestions from the experts?

You've got a couple of options...

1) Set<configuration><system.web><compilationdebug="false">in your web.config

2) Set theScriptMode="Release"property on the ScriptManager component

<asp:ScriptManagerID="ScriptManager1"runat="server"ScriptMode="Release"></asp:ScriptManager>

Either way, you should end up with the release version of the javascript coming down to you which is A LOT faster!!

Make sure you've got the 10301 release as well - there were several Calendar perf fixes in that release.

Thank you very much for both of your responses... I tried the latest update and, yes its fast now!

Now it'll be easier to hookup pop-up calendar functionality using the Calendar Extender, without worrying about performance.

I set theScriptMode="Release"in the Script Manager too, asJames_2JS suggested, hope it also contributed to the improvement.

Can you explain what these changes do?