<div>
Ya it is been replaced with EWS. Now you can you EWS
</div>


Ya it is been replaced with EWS. Now you can you EWS

<div>
So any client code that uses WebDAV will not work?
</div>


So any client code that uses WebDAV will not work?

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
Our exchange server is going to be soon upgraded from 2003 to 2010.<br />
<br />
Currently we have a small number of client apps (written in JavaScript and C#) which use the WebDav protocol to manipulate calendar items in Exchange.<br />
<br />
When we upgrade to 2010 are these applications going to break and will they need re-writing to use EWS ?<br />
<br />
I have done some initial research and I know that WebDev is being depreciated and no longer supported by Microsoft. <br />
<br />
What I don't know is if WebDav is just not supported, or if it has been completed removed from the newer versions of Exchange.<br />
<br />
Can someone shed some light on this please?
</div>
</div>


Hi,

Our exchange server is going to be soon upgraded from 2003 to 2010.

Currently we have a small number of client apps (written in JavaScript and C#) which use the WebDav protocol to manipulate calendar items in Exchange.

When we upgrade to 2010 are these applications going to break and will they need re-writing to use EWS ?

I have done some initial research and I know that WebDev is being depreciated and no longer supported by Microsoft. 

What I don't know is if WebDav is just not supported, or if it has been completed removed from the newer versions of Exchange.

Can someone shed some light on this please?

Can I use WebDav on Exchange Server 2010

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).