NuGet Update - Exchange 2016 version

OfficeDev / ews-managed-api

Other

585 stars 319 forks source link

NuGet Update - Exchange 2016 version #149

Open VlatkaFundak opened 6 years ago

VlatkaFundak commented 6 years ago

can you please update NuGet package in order to use added Enum for Exchange Server 2016 version? Thanks

Misiu commented 6 years ago

Also please add Office365 in ExchangeVersion. This way we could do this new ExchangeService(ExchangeVersion.Office365). I'm aware that selecting Exchange2013_SP1 works, but Office365 could be an alias and it "feels" better.

chrisnott commented 5 years ago

Come on please, this seems ridiculous. How long would it take for someone to package the latest version and update the nuget feed? This screams of 'I don't care'. Please help us. We need this as not all people will move to O365/Exchange Online. Seems bonkers to expect everyone to download build and reference manually - this is what NuGet is for!!!

MichelZ commented 5 years ago

Microsoft „Moved on“ from this project. We have to accept it and establish/support a proper fork

igitur commented 2 years ago

I accept that they don't maintain this anymore. But they really can at least just update the Nuget package to match the current source code.

MichelZ commented 2 years ago

Well, you just need to accept that this project has been abandoned by Microsoft. EWS is dead for them, they have plans to remove the ability to use new Applications with EWS in EXO. (i.e. they plan to remove the ability to register new azure ad applications with the EWS permissions)

There are forks around that include some of the PR's and the latest code. Or it's fairly trivial to create your own package and host it e.g. on your own azure devops instance.