Make Exchange 2010 coexist with Exchange 2003 in the same domain

Useful links:

http://www.jesswatts.com/it/exchange-owa-redirect

http://www.ipsure.com/blog/2011/outlook-web-app-access-in-an-exchange-2010-%E2%80%93-exchange-2003-coexistence-scenario/

Raise Forest (Domain) Functional Level - Exchange 2003

- Log into DC machine.
- Start -> Administrative Tools -> Active Directory Domains and Trusts
- Right-click on Active Directory Domains and Trusts -> Raise Forest Functional Level...

- Right-click on domain name -> Raise Domain Functional Level...

Use Proxy Server in your browser

Here is a link with free Proxy Server IPs you can use in your browser:
http://www.samair.ru/proxy/ip-address-01.htm

Here are the settings you need to do for different browsers:

1. Internet Explorer and Chrome: [Tools ->] Options -> Connections:

2. Firefox: Tools -> Options -> Advanced -> Network -> Settings:

Cannot find System.ServiceModel.Web reference

This is caused by the targeted Framework.

By default Visual Studio 2010 comes with .Net 4 Framework Client Profile (for desktop applications). The System.ServiceModel.Web.dll is not available in this case.
The targeted framework should be changed to .Net 4 Full.
Here are the steps:
1. Right click on the project where you want to add the System.ServiceModel.Web reference.
2. Go to the Application tab.
3. Choose .Net Framework 4.

Website Testing Techniques

One of my coleagues mentioned this link:

http://www.codeproject.com/KB/testing/WebsiteTestingTechnique.aspx

Thanks Edi!

Cannot implicitly convert type 'EvalServiceLibrary.Eval[]' to 'System.Collections.Generic.List'

For this error ,

You need to add '.ToList<Eval>();' at the end of the line, so that both parts are of the same type.
This is how the 'case "list":' should look like:

and the 'GetEvalBySubmitter(name)' like this:

Cannot load the X.509 certificate identity specified in the configuration

To overpass the "Cannot load the X.509 certificate identity specified in the configuration" error, check the above solution.

Solution (it's fast, not necessarily the best approach): 

Remove the following lines from all places in App.config.