Well, I could do that call from there, but I don't.
The lock is static because the resource to be protected is - behind some wrapping - a serial port. I.e. hardware which is shared by all the commands to be sent over that port.
The issue has to do with the fact that R# can't guarantee that you're using _SomeMember inside a synchronized object. In your derived class, you could call Step5 without going through the DoSomething route so R# is doing its best to warn you that you MAY have issues, not that you do have issues.
Sorry to come back here for this, but I have a short question regarding ReSharper (I'm thinking about to buy it).
Does ReSharper warns me in case I do use IDisposable classes without proper using of using or try/catch?
Thank you in advance.
If you're looking for a C# library that means the finger print scanner would have to be connected to the web server. That's probably not going to happen. ALL ASP.NET/MVC code runs entirely on the server, not the client.
I am running this from one domain and against a different domain. The process is incredibly slow and I'm wondering how I can speed my code up so that instead of it taking 20 minutes, it will only take 1 minute.
I have noticed that every once in a while it will only take 1 minute and I'm wondering if I need to point it to a specific DC in the domain I am looking through or maybe something else?
This doesn't make a lot of sense. Are you getting all of the group memberships of a specified user or are you getting all of the group memberships of a list of users who are members of a specified group, or what?
You never spelled out exactly what this code is supposed to be doing.
There is a starting parent group, and I'm starting with the parent and enumerating through all of the child groups of that parent and every group that is a member of the child groups that are found. At my organization, there may be a nested hierarchy of 12 groups or more and unfortunately there may be some of the same groups nested in other groups as the local admin qualification is to have a pulse.
If you are making a request to the domain controller for every group at every level, you're going through an expensive operation, every single time. Just because you're code hits one domain controller for one request does not mean that the same domain controller is going to service all subsequent requests. You could be throwing requests all over the network without knowing it.
Now, each request is expensive so it would be better to make them once and then cache the result. Create a Dictionary to cache the objects returned. When you make a request for a group, lookup the group name in the cache to see if it's there first. If not, go to the directory to get it and cache it for use next time around. Whenever you go get a list of groups, add them to the cache if needed.
They don't really work together, do they? Either we create it or you do: us giving you a program is not "you creating" it.
In the first case, no. We are not a "code to order" service.
In the second case, we expect you to try and do it yourself: then you can ask if you get stuck. Just going "give me the code" is not going to get you helped much...if at all.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Last Visit: 31-Dec-99 18:00 Last Update: 23-May-22 8:36