I had the same problem when using the EWS. My Code is requesting the events(Appointments) from the.
I had the same problem when using the EWS. My Code is requesting the events(Appointments) from the Outlook calendar, at the end I couldn't reach to the body of the Event itself. The missing point in my situation was the following "forgive me if there is any typo errors": After gathering the Appointments, which are also derived from EWS Item Class, I did the following: 1- Create a List with the type Item: List items = new List(); 2- Added all appointments to items list: if(oAppointmentList.Items.
Count > 0) // Prevent the exception { foreach( Appointment app in oAppointmentList) { items. Add(app); } } 3- Used the exchanged service "I have already created and used": oExchangeService. LoadPropertiesForItems(items, PropertySet.
FirstClassProperties); now if you try to use app.Body. Text, it will return it successfully. Enjoy Coding and Best Luck I forgot to mention the resource: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/thread/ce1e0527-e2db-490d-817e-83f586fb1b44 He mentioned the use of Linq to save the intermediate step, it will help you avoid using the List items and save some memory!RockmanX.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.