|
from memory, you never get an 'exact' 'timeout'
I'm a bit worried about Quote: but the bind doesn't timeout after 10 seconds
are we talking about the same thing ? if you bind successfully, you wont be timed out - the Timeout setting is to set a time +/- a factor that may depend on your network/the MSAD/LDAP server, that says 'time me out if I cant connect/bind to the server within this time'
(it could be that my understanding is wrong of course)
|
|
|
|
|
Hi Garth,
Thanks for your reply.
Indeed, if the bind is successful... no time out and everything is fine.
My concern is when the bind isn't successful ("server not reachable" for example): I want to 'time out' if the bind hasn't been established within (for example) 10 seconds.
I did the test with the code I posted setting the timeout on 5 seconds: the time out was not near the 5 seconds... it gets up to 90seconds. 
So, it seems that or my code is wrong or the 'timeout'-property is not used for this purpose...
Thanks,
Marc.
|
|
|
|
|
hmmm, well, obviously you're using System.DirectoryServices.Protocols LdapConnection otherwise the Timeout property wouldn't be exposed (System.DirectoryServices was the old model that didn't expose/honour any timeout)
I wouldn't have expected 90 seconds though, and unfortunately these days I'm not in a position to test for you .. are you sure you're timing the right thing (sorry to play 'second guess a pro')
what happens if you put
stopWatch.Start();
connection.Bind();
stopWatch.Stop();
TimeSpan ts = stopWatch.Elapsed;
string elapsedTime = String.Format("{0:00}:{1:00}:{2:00}.{3:00}",
ts.Hours, ts.Minutes, ts.Seconds, ts.Milliseconds / 10);
Console.WriteLine("Bind Time " + elapsedTime);
|
|
|
|
|
Indeed, I 'switched' from System.DirectoryServices to System.DirectoryServices.Protocols in order to have the property 'Timeout' at my disposal.
I've timed like you suggested... and no surprises (for me) 
- when no problem : 00:00:00.18
- when problem ("server not reachable") : 00:00:50:05 (and above)
|
|
|
|
|
obviously I don't know your network environment, whether your client is on one subnet and the MS AD/LDAP server on another (routing issues) and what other factors may be involved - MS AD/LDAP running on an under-powered server or all sorts of things in-between
if
MarcSchmidtmayer wrote: 00:00:50:05 (and above)
is hard to swallow - if you have a user looking at a GUI I'd suggest authenticating in the background and keeping the user happy, if its a high speed automated process or something, well, if you cant get a better response time to the server via the network/increase server threads/performance etc I'd be thinking about some 're-architecting' of the software stack, caching ...
|
|
|
|
|
Unfortunate is the fact that I can't make up if it's the 'TimeOut'-property that doesn't work
(like I think) or that it is a 'network issue'. 
When I read your answers, I guess you also believe that the 'TimeOut'-property should work...
Anyhow... thanks for your answers and suggestions... 
Don't forget to let me know whenever you should haven another 'idea'... 
|
|
|
|
|
there is no timeout property for Bind. no solution found for .net core.
Kamran Shahid
Sr. Software Engineer
(MCP, MCAD.net, MCSD.net, MCTS, MCPD.net[web])
Netprosys Inc.
www.netprosys.com
|
|
|
|
|
Wow, your internet connection must be terrible! Your first post in over eight years, and it's a response to a thread from 4½ years ago. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Probably a 600 baud line.
|
|
|
|
|
hehehehehehehhehehe
Kamran Shahid
Sr. Software Engineer
(MCP, MCAD.net, MCSD.net, MCTS, MCPD.net[web])
Netprosys Inc.
www.netprosys.com
|
|
|
|
|
There is a way to get QuickSharp to run your program in a separate window but I can't find any info on this. Anyone have any insight into this?
|
|
|
|
|
|
I assume you are talking about the version on SourceForge. You would be better off asking questions like this on the forum there. Alternatively, you could read the documentation[^].
This space for rent
|
|
|
|
|
microsoft report viewer simple invoice format code c#
send me full code
how to add grid in report viewer
|
|
|
|
|
|
It doesn't quite work like that.
We do not do your work for you.
If you want someone to write your code, you have to pay - I suggest you go to Freelancer.com and ask there.
But be aware: you get what you pay for. Pay peanuts, get monkeys.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Member 12951091 wrote: send me full code
send me full payment.
$3,000 USD will do for a deposit to establish your requirements.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
My issue is trying to understand where and how platform specific code can be used. i.e. hearing Raspberry PI will support .NET Core I thought "Hey, how I write a UI for that"? But the question might not make much sense. So let's see if I got things right.
.NET Standard: a .NET Standard library target no particular environment and should be supported on all platform that support that Standard library level. These are the new PCL (with a little less hassle).
.NET Core: A multiplatform .NET runtime execution environment. Much like the .NET Framework itself. Except it has less API and more platform support. It can execute latest .NET Standard library as well as .NET Core library.
.NET Framework: A Windows specific .NET runtime and execution environment.
Xamarin Android: An android specific .NET Runtime and execution environment. Can execute Xamarin library as well as .NET Standard library (though some some .NET Standard library calls throw "NotImplementedException" as of now! )
Now if I want to write a PCL UI library that will run on Android I need to delegate some call to some interface / type that will be registered by the Xamarin Android execution environment at startup before it starts the PCL library.
Similarly I am confused as to one do platform specific code in .NET Core. Since I start the .NET Core environment directly (as opposed to a .NET environment specific to the host), how could I stub in native UI technology?
|
|
|
|
|
|
Thanks.
I spent the whole evening yesterday playing with various cross framework compatibility (.NET Standard 1.6, .NET Core, .NET Framework, Xamarin iOS, Xamarin Android, UWP) and I have the feeling the whole thing is... unfinished...
For example, .NET Standart 1.6 is compatible with an, as of yet, unpublished version of the .NET Framework! 
Or my .NET Standard 1.6 library was correctly linked into Xamarin Android but had post compile error (creating debug info) with Xamarin iOS, and some method threw NotImplementedException when run on Android.
Anyhow it looks like one will have to wait for .NET Standard 2.0 for better compatibility story, which, last year, they said should be around VS2017 release date....
|
|
|
|
|
Agreed. The rate of improvement and the expansion of the knowledge base will be proportional to the rate of adoption; unless one is adventurous ... or someone else is paying for the adventure.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
|
I will have to wait for 2.0...
Not only tooling and compatibility should be better. But they will have a mechanism in place by then to access the native framework as well... wonder how it will work (they just mention it, but it's not available yet)
Thanks anyway! 
|
|
|
|
|
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
|
|
|
|
|
We can't tell either: you need to read the error message carefully and do what it says.
It tells you exactly what you need to do to get the actual error report to be visible - message, stack, the whole enchilada. Do what it says, and it will tell you which file, which line is caising a problem, and what problem has been detected.
But until you have that, nobody can fix anything.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
