|
Hi all.
For some reason, whenever I open a project in vb.Net 2010, and open a document, it scrolls uncontrollably to the bottom of the page. I can't get it to stop.
What's up.
|
|
|
|
|
Get your damn parrot off the keyboard.
|
|
|
|
|
|
That gives a new meaning into hunt 'n peck typing. 
|
|
|
|
|
Lol! There you go.
...That's a true story by the way. Happened this afternoon. 
|
|
|
|
|
I have a utility which loops through our LDAP fetching all of the CN values out to a .csv file, I am validating this against an Excel document which contains our phone number list. The problem is that for some people, I do not find a LDAP entry.
I have another utility which takes as input the Username of someone and dumps out all of the attributes found in our LDAP and when I use this utility to find a person which is not listed on the main dump file, I do find him. 
I wrote both utilities, so the fetching logic is very similar.
The looping utility uses:
Dim de As New DirectoryEntry("LDAP://DC=us,DC=myCompany,DC=com")
ds.Filter = "(&(objectCategory=person))"
While the single user verifier uses:
Dim de As New DirectoryEntry("LDAP://DC=us,DC=myCompany,DC=com")
ds.Filter = String.Format("(SAMAccountName={0})", Me.tboxUserName.Text)
I have looked at the LDAP properties of 2 users; UserA is the guy I don't have in my .csv file and UserB who is listed in the .csv file and nothing obviously jumps out at me being different.
Where should I be looking to resolve this issue? If I can find a user directly by his username, then he should be part of the .csv export file. Right?
Thanks in advance for your guidance.
|
|
|
|
|
The obvious place to start is the objectCategory. If you modify your second example to:
ds.Filter = String.Format("(&(objectCategory=person)(SAMAccountName={0}))", Me.tboxUserName.Text)
can you still find the missing user?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Tried your suggestion and the answer is YES, I could find the user with that criteria.
I'm using the following code in my "Ldap Dump" routine:
For Each sr As SearchResult In ds.FindAll()
I thought I read somewhere about getting LDAP information in "pages". Am I OK by using the above logic to extract the user list?
This is really a head scratcher.
|
|
|
|
|
David Mujica wrote: ds.Filter = "(&(objectCategory=person))"
Sounds like a collection of "all persons".
David Mujica wrote: (SAMAccountName={0})
Sounds like a more specific collection; is there a person that's not a user? A disabled user?
http://www.ldapexplorer.com/en/manual/109050000-famous-filters.htm[^]
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
By combining the objectCategory=person and SAMAccountName={0} into one filter, I am capable of finding my user.
The problem seems to be that when I loop through the LDAP, I'm not getting all of the users.
|
|
|
|
|
Got it !
I added the following to my code and now the user in question is showing up in the "LDAP dump" file.
ds.PageSize = 2000
Thanks to all for replying to my post.
|
|
|
|
|
Thanks for posting the resolution.
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
Howdie.
Has anyone encountered vb.Net reversing your edits to a project?
I just spent two days looking for a problem that took me so long to figure out because I had previously made some edits that I know were fixed, so I did not go back there until it was obvious the problem was there....Again! I had about 5 win32 functions that I needed to change from Private to Public, and a few ByRef that needed to be switched to ByVal. I was testing the program fine for a few days WITH THOSE FIXES ALREADY MADE, when all of a sudden I was getting odd errors that were hard to nail down":
"Cannot evaluate expression because the code of the current method is optimized."
and
"Exception of type 'System.ExecutionEngineException' was thrown."
The first error was difficult to nail down because it was silent and GetLastError() just returned 0 (function executed successfully), and the last error gives no indication of the problem source. Fortunately the last error went away with the solution to the first.
Basically what vb.Net did was change two of my Public back to Private, and switched one ByVal back to ByRef.
Very strange.
|
|
|
|
|
This may not be VB's fault at all, there are a couple things that could be going on...
First, if you had to do a disk repair or roll back (restore from an older version of the disk) then some disk changes may have been rolled back to old values. These roll backs can happen when you install software almost silently so its important to watch if the installer says "creating restore point".
Second, maybe you had the project open in two instances of visual studio, edited it in one, saved it, then in the other it usually says "the file changed would you like to reload" or something like that. If you don't read it quick then dismiss the dialog, make a change there and save it, it will overwrite your changes from the other instance.
Another thing is that you could have been editing the file in a sand box. Sometimes your anti-virus software incorrectly sandboxes some programs, you can make all the changes you want, compile, run, everything looks great until you exit the program and your changes aren't saved to disk. This is especially annoying and difficult to find, make sure that your antivirus hasn't sandboxed your Visual Studio instance.
Other than that, I really can't think of any reason that visual studio would "roll back" changes to your files, especially after saving them to disk.
|
|
|
|
|
Thanks for your reply, Ron.
There were no rollbacks, multiple instances open, or sandboxes running. But I have heard from somewhere along the line that some people have had a problem with making changes, and running it in the IDE and it behaving as if no changes had been made. I guess it boiled down to something involving the latest build vs. a cached build. One guy reported that even if he exited vb and came back in, the problem was still there, until he rebooted, and everything was OK. I could not reboot only because I am running a 3D rendering that must keep going.
My problem is different than those, but was wondering if they aren't related in some way.
|
|
|
|
|
Quote: But I have heard from somewhere along the line that some people have had a problem with making changes, and running it in the IDE and it behaving as if no changes had been made.
That can happen when the source file somehow becomes post-dated in regards to your computer's time. Shutdown VS, fix the file date-time, delete the bin and obj folder contents.
How can this happen? Work on a project with someone on the other side of the world by exchanging files is how.
|
|
|
|
|
NOW I KNOW WHY THAT HAPPENS! Often, I will try to finish up a project development date-version by 12:00 midnight. I do that so that my dated project folders show up consecutively in Windows Explorer. I also put the date stamp in the project name, in case I wrote the date incorrectly and it does not match up with the Windows date stamp, or if I archive a folder much later than I should have (since Windows does not preserve the original modification date of the folder when it is copied). Just an extra layer of info to help keep things organized. But if I forget to close out by 12:00am and catch it within maybe half an hour, I will set my clock back to just before midnight of the previous day, save out, then copy that project folder over to a new one with a new date stamp in the title.
|
|
|
|
|
treddie wrote: Basically what vb.Net did was change two of my Public back to Private, and switched one ByVal back to ByRef.
Very strange.
I'd rather call that "unlikely" than "strange". What reason would it have to do so?
Edit it again, and have it write it's version (or anything else you'd wanna use to discriminate between your current code, and the previous) to a file, or, better yet, using OutputDebugString. Weird, spooky stuff like this can happen if part of the code is outdated, which can happen through a multitude of ways.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
I'll google "outdated code" and see what comes up. Another issue that might be related is for some reason a form will fail to refresh due to controls being "missing" when they were in fact always there. I find it odd that vb can lose track of controls on a form without me having made any edits that directly affect a control.
|
|
|
|
|
treddie wrote: I'll google "outdated code" and see what comes up.
Ah, sarcasm, the most honest forms of poetry; Google for ..
Here[^]'s the link. In short, your app might pick another assembly than you expect it to, depending on the location of the assembly, it's version and some other stuff.
treddie wrote: Another issue that might be related is for some reason a form will fail to refresh due to controls being "missing" when they were in fact always there. I find it odd that vb can lose track of controls on a form without me having made any edits that directly affect a control.
It didn't, otherwise it could not claim it to be missing. It knows what control is expected, but the complaint mentions that it did not find physical code there. Or anywhere else in it's search-path. Often, it's because it's either too picky (compiled against a specific version) or not picky enough (using an older version of the assembly that's higher in the searchpath).
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Heheh...No sarcasm intended. I don't expect people to feed me on a silver platter, so I was going to go search for it on my own.
I read the article, and that seems pretty messed up. I mean, If I'm writing a program, and I have my code sitting there, it should be the only code referenced. After all, I just spent the time to edit it...I expect it to be current without some shady things going on in the background.
As an update, I forgot to mention that the form was not refreshing IN THE IDE. I'm sure you've run into that, where you click on, say, the Form1.vb [design] tab, and instead of the form popping up with all its controls, you instead get an error screen telling you something bad happened and the form can't be displayed.
|
|
|
|
|
treddie wrote: I read the article, and that seems pretty messed up.
It is
treddie wrote: As an update, I forgot to mention that the form was not refreshing IN THE IDE.
The runtime still has to resolve the assembly, giving the same problems.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Ahhh, but of course. Unless the compiler has a magical fix.
|
|
|
|
|
No insult intended, but never underestimate the frustration caused by pilot error when using Undo.
|
|
|
|
|
No insult taken. You may be exactly dead on correct, there, in my case!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
