shared

Our Exchange Admins (Exchange 2010 SP1) have setup a shared resource calendar. There is no mailbox assigned to this resource calendar . I want to be able to read the meetings using EWS and C#. Snippet: ExchangeService esvc = new ExchangeService(ExchangeVersion.Exchange2010); esvc.Credentials = new WebCredentials(username, password, "ourplace.org"); esvc.Url = new Uri("https://OWA.OURPLACE.ORG/EWS/Exchange.asmx"); FolderId shareFolderId = new FolderId(WellKnownFolderName.Calendar, "Shared Calendar Name"); CalendarFolder.Bind(esvc, shareFolderId); the bind statement throws the error: "The SMTP

I'm get kind of getting mixed messages about this so I'm hoping someone can clear this up for me. Should I be using Shared methods/functions in the following situation: I have a generic class named "Person". This class represents a person in the database. I have a manager class named "PersonManager". This class contains methods which adds, updates, deletes individual Person objects. A method also exists to lookup Persons from the database. Should these methods in the manager class be declared as shared methods? Or is it more appropriate to create a new instance of the PersonManager class each

The Windows API offers the CreateFileMappingNuma function ( http://msdn.microsoft.com/en-us/library/windows/desktop/aa366539(v=vs.85).aspx ) to create a named shared memory space on a specific NUMA node. So far, I have not found an equivalent function for Linux. My current approach looks like this: Allocate named shared memory (using shm_open(...)) Determine current NUMA node (using numa_move_pages(...)) Move pages to target Node (using numa_move_pages(...) again) Does anyone know a better approach? EDIT: For the record: My proposed implementation does work as expected! That sounds right. Note

I wonder why Visual Studio is raising this warning: Access of shared member, constant member, enum member or nested type through an instance My code: Dim a As ApplicationDeployment = deployment.Application.ApplicationDeployment.CurrentDeployment If System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed Then If a.IsNetworkDeployed Then ' do something End If End If What implies "through an instance"? Also, why is this a "warning"? Showing a warning is a design option. In C#, it would throw an error when calling a static using an instance ( this ) keyword. The problem is that you

first, Thank you read this :) I use DLL shared Memory and using interlocked~ functions. (Win 7) DLL loaded by service exe and user app exe. you know, service session is 0, user session is 1 so different. if DLL's shared memory value changed by user app exe, not reflected service's DLL shared memory value. is there a way to sync service and user app's DLL shared memory? Shared sections don't work across session boundaries any more. Microsoft considered this a security problem and deliberately broke the feature, quite some time ago if memory serves. I believe each session now sees its own

I am considering using a Shared (read static) WCF proxy client for a high throughput application. I believe there is a performance gain in doing this, but I have not benchmarked this as yet. Are there some serious pitfalls to this idea? From my research I can see that there is the issue of handling the fault state, it is not clear what the flow on affect of this state would be to other pending requests. Does anyone have any experience recovering a WCF proxy from it's faulted state? thanks in advance! Once the channel is in a faulted state it will stay that way. So yes, I think a static client