Skip to main content

Exchange Web Service - query problems

Exista mai multe versiuni de Exchange Server, majoritatea serverelor care exista la ora actuala sunt 2007 SP1 si 2010. Daca vrem sa scriem o aplicatie care acceseze direct contul de Exchange puteti sa folosim un client care consuma serviciile expuse de acest server precum EWS - Exchange Web Service. Aceasta este doar un assembly pe care trebuie sa il adaugam la proiect. Pregatesc in aceasta luna mai multe tutoriale despre EWS. In postul de azi vreau doar sa subliniez o problema pe care EWS o are. O sa vorbim mai in detaliu cu alta ocazie despre cum sa il folosim.
Exchange Server 2010 a adus cateva schimbari la nivelul entitatiilor care exista. De exemplu pe 2010 un contact poate sa aibe atasata o poza sau modul in care sunt grupate contactele difera fata de 2007. Din pacate EWS ne aduce datele in functie de versiune de Exchange pe care o accesam.
Un exemplu destul de bun, pentru a arata problema care o are EWS este cand vrem sa aducem lista de contactele a unui account. O sa ne trezim ca versiunea 2007 SP1 ne aduce obiecte de tip ExpandGroupResult, pe cand 2010 ne aduce obiecte de tip GroupMember.
Aceste probleme ma sperie, nu neaparat ca trebuie sa scriu un IF in plus, nu ar fi nici o problema, dar ce o sa ne facem cand apara urmatoarea versiunea de Exchange? Cand o sa dorim sa ne conectam la Exchange Server 20xx o sa ne trezim ca aplicatia crapa, deoarece rezultatele pe care il primim difera. Notiunea de backward compatible nu exista in acest caz si nici notiunea ca o metoda ar trebuii sa returneze un singur tip de data sau macar datele returnate sa aibe o interfata comuna, daca nu un base class.
Principala problema asa cum o vad eu vine de la libraria EWS. Chiar daca ea primeste de la server date de tipuri diferite, ar trebuii sa expuna consumatorului date de aceleasi tip.
Nu stiu ce schimbari o sa aduca urmatoarea versiune de Exchange, dar mentenanta pe aplicatiile care folosesc EWS nu o sa fie tocmai atat de placuta.

Comments

  1. Oare si ActiveSync are aceleasi probleme de backward compatibility?

    Am banuiala ca Exchange (ca si Lotus Domino), nu prea au fost gandite de la bun inceput sa fie folosite in mod curent de aplicatii externe third-party, ci mai degraba s-au focusat pe development-ul de aplicatii bazate pe clientii proprii, gen Outlook sau Lotus Notes.. (gen formuri cu VBScript respectiv LotusScript in spate..)

    ReplyDelete
  2. Cand faci public o librarie care este mapata peste propriile tale servicii, ma astept sa fie consistenta sau macar documentata.

    ReplyDelete
  3. Adevarat, asa ar trebui sa fie.. Din pacate, cu cat un API/web service e folosit de mai putine persoane, cu atat unii autori se simt mai putin motivati sa mentina backward/forward compatibility..

    ReplyDelete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…