See Attached Sample App (The required/referenced DLLs where too large so they are in the second attachment)
Replace the EWS Endpoint with one that is associated with a valid account.
Login
The following lines of code execute without error. Running Fiddler DOES show traffic Successfully retrieving information from the EWS Endpoint, but the XamOutlookCalendarView never updates and does show any information or any indication of success, it looks like nothing has happened even though through Fiddler the web traffic can be verified.
ewsCredsExchangeConnector.Users = userList;
ewsCredsExchangeConnector.UseDefaultCredentials = false;
ewsCredsExchangeConnector.ServerConnectionSettings = new ExchangeServerConnectionSettings();
ewsCredsExchangeConnector.ServerConnectionSettings.RequestedServerVersion = exchangeVersion;
ewsCredsExchangeConnector.ServerConnectionSettings.Url = ews.Url;
ewsCredsExchangeConnector.Connect();
Hello Jesse,
Thank you for contacting Infragistics!
I have been looking into your issue and it seems that for some reason the second attachment that you are referring to have not passed through. Would you please re-send your attachments using Internet Explorer or Mozilla Firefox and send them as zip file in order to ensure that the files will be received successfully?
Also when I have downloaded the attachment and run the .exe, that was inside. I saw, that there was TextBoxes for username and password. Do I have to insert username and password. If yes, what would they be?
Would you please provide me with further steps, that I can follow in order to reproduce the issue you have mentioned.
Looking forward to hearing from you.
I have attached the DLLs as a .zip, as far as the EWS credentials, I assume/hope that you or someone you work with on support issues uses Outlook and can find their Exchange Endpoint to login and prove out my reported issue. This is not specific to a particular user or Exchange Server, we have seen the Infragistics Calendar Show Blank when connected to a few different accounts & Exchange Servers.
Did you confirm that there is an issue w/ the version of the Controls that I originally reported (13.1)? And that everything works as expected in 15.1?
I ask because upgrading our controls is not an option at this time.
Please confirm, thanks
Please see my prior post on 13.1 versus 15.1, additionally, unless you can tell me more it looks like the newer sample app that you had sent also does not render/update.
I have modified it to not use Domain when constructing the ExchangeUser object, this seems to be what causes the problem. I want to point out that while running Fiddler we can see network traffic successfully returning data, but the Calendar does not update or render (When Domain is not added to the construction of the ExchangeUser object).
I have logged this behavior with our developers in our tracking system, with an issue ID of 208335. I have also created a support ticket on your behalf with number CAS-165513-W2G4Z7 in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.
Thank you for your patience during the investigation for your issue. After the development team researched your issue with ID of 208335 they reached the conclusion that the issue is based on used approach to how you are trying to connect to the exchange server and when you are trying to hook to the CollectionChanged event. The CollectionChanged event should be registered before the changes have already taken place. This is why you should hook the CollectionChanged event immediately after you have Connected to the ExchangeConnector and not on a separate button. Just keep in mind that the adding of activities in response to CollectionChanged, will not reliably fire for these reasons and that's why you should hook before some change is made to the collection.
Also the specified ScheduleDataManager.CurrentUserId should correspond to the information provided to the ExchangeUser constructor. If you are not specifying domain in the ExchangeUser constructor then the CurrentUserIde should be only "\\USERNAME"(with backslash prefix) it will then math the information provided to the ExchangeUser constructotr and the schedule will load.
I have created a modified sample showing how to do the connection to the exchange server with and without a domain.
Please review it and if you have any further questions do not hesitate to ask.
Sincerely,TeodorInfragistics Inc.www.infragistics.com/support
Hello,
I am just checking your progress on the issue that you are having.
If you require any further assistance please do not hesitate to ask.
Thanks,
Teodor
Software Developer
Infragistics
www.infragistics.com/support