|
|
Honestly, and in this day and age! Clickety[^]
If the post was helpful, please vote, eh!
Current activities:
Book: Devils by Fyodor Dostoyevsky
Project: Hospital Automation, final stage
Learning: Image analysis, LINQ
Now and forever, defiant to the end.
What is Multiple Sclerosis[ ^]?
|
|
|
|
|
Collin Jasnoch wrote: like it is illegal to grow a chicken in a bottle
Curses! Foiled again!
|
|
|
|
|
Bah, amateurs... If not for that silly law, you would all be welcoming my bottled chicken overlords. 
|
|
|
|
|
In Nebraska it is illegal to poach whales.
In Virginia there is a state law prohibiting “corrupt practices of bribery by any person other than candidates".
-Brian
|
|
|
|
|
Just kidding.
But you just know that some of the folks around here have been thinking about it. 
|
|
|
|
|
I don't know but I suspect you'd have to unplug the blender 3 times before you can load the damn thing into it!
|
|
|
|
|
Apparently, yes.[^]
And now you see the genius of Microsoft's Marketing Department (but who still remain a bunch of mindless jerks who'll be the first against the wall when the revolution comes).
|
|
|
|
|
Aww, give them a LITTLE credit... They're not quite as bad as Sirius Cybernetics.
|
|
|
|
|
Thought that was Cyberdyne...
|
|
|
|
|
Cyberdyne Systems = Creators of Skynet from the Terminator series
Sirius Cybernetics = Creators of annoying robots from Hitchhiker's Guide to the Galaxy
...the Marketing Division of the Sirius Cybernetics Corporation defines a robot as, "Your plastic pal who's fun to be with!" The Hitchhiker's Guide to the Galaxy defines the Marketing Division of the Sirius Cybernetics Corporation as "a bunch of mindless jerks who'll be the first against the wall when the revolution comes", with a footnote stating that the position of Robotics Correspondent is vacant. It is notable that a future edition of The Encyclopedia Galactica fell through a wormhole in time, and its entry for the Sirius Cybernetics Corporation is "a bunch of mindless jerks who were the first against the wall when the revolution came."
-- Hitchhiker's Guide to the Galaxy (from WP[^])
|
|
|
|
|
Thank goodness I had my towel when I read that, otherwise I would have spewed coffee on my office mates.
|
|
|
|
|
You've really got to know here your towel is. No fooling.
|
|
|
|
|
I'm also strongly considering changing the title of all my error dialogs to DON'T PANIC.
|
|
|
|
|
Just PANIC will do. Probably more effective, also
|
|
|
|
|
martin_hughes wrote: Probably more effective, also
Yea ... I probably should stop using that animation of a nuke on the dialogs uh?
|
|
|
|
|
Blending ... 99% complete ...
|
|
|
|
|
But just think of all the good we could do if we were helping our local church in a soup line instead of developing software!
Marc
|
|
|
|
|
Clippy: "It appears that you are trying to... aaaaaaaaaahhhhhh! ouch! ouch! ouch!... blend a... aaaaahhh!!!..."
|
|
|
|
|
This morning VS 2010 did not stop on a break point, but the code executed. Has anyone else experienced this?
On a positive note, I was debugging a new application with a couple consultants and we tried to view the value of an object not in memory. I clicked the reverse arrow and VS reloaded the object into memory. The three of us all had this ridiculous grin on our respective faces. It was the first time any of us had ever been able to debug in reverse.
I didn't get any requirements for the signature
|
|
|
|
|
Does it keep a history in cache or something?
Todd Smith
|
|
|
|
|
I don't know. We were using an API to save an item in an application. We had a break point set to check the value being set and it never stopped. Then we viewed the ticket on the projector and the value appeared on the screen in the application. There were two other developers in the room and we were like "WTF". So I tried it two more times and the break point was never hit. But the value was set. It was strange.
I didn't get any requirements for the signature
|
|
|
|
|
Have you tried disabling the automatically jump over properties 'thing'?
It's a very wild guess, and I'm obviously assuming you're breakpoint is actually in a property, but it might be worth a try.
|
|
|
|
|
ToddHileHoffer wrote: This morning VS 2010 did not stop on a break point, but the code executed.
I occasionally (but rarely) experience this in VS2008. I usually have to delete all breakpoints, but failing that, doing a full rebuild always fixes the problem.
Marc
|
|
|
|
|
The only time I've seen this happen it turned out I was in release mode not debug; or something up the calling chain had a debugger ignore attribute. 
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
