The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Sometimes I accidentally leave my project in "Release" configuration, and I barely notice or don't notice at all.
The debugger attaches, breakpoints hit, and unlike C++ I have the entire stack frame and everything else at my fingertips, in C#, just like in debug mode.
There's very little actual code optimization done at this phase, or at least that used to be the case, and based on a little test @Super Lloyd (don't know how to tag here) ran some time back still seems to be. This is perhaps Microsoft's dirty little secret, they don't do much whole program optimization.
But mostly, the debugger works great because all the type information is there, even release, so you have the offsets of every member, and all the names.
It almost raises the question of why bother even having debug mode in .NET aside from conditional compiles (#define DEBUG) and metadata attributes related to it.
I think i may have hit a snag hitting a breakpoint in some scenarios but most of the time everything just works.
Not that I recommend this. I just find myself in release without noticing for awhile because of it.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
It's pretty simple.
In many cases you can just use an "@", followed by the username: @OriginalGriff
And the system will replace it with the link, and send the email as it did with me.
But yours is harder: @honey the codewitch won't work, because that isn't what you started with, and it contains spaces. So I go to your homepage, and below your username is the correct code: @code-witch
For Super Lloyd, you do the same thing, and get @Super-Lloyd which is who you were trying to acknowledge.
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
The Beer Prayer - Our lager, which art in barrels, hallowed be thy drink. Thy will be drunk, I will be drunk, at home as it is in the tavern. Give us this day our foamy head, and forgive us our spillage as we forgive those who spill against us. And lead us not to incarceration, but deliver us from hangovers. For thine is the beer, the bitter and the lager, for ever and ever. Barmen.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
I never paid more than 50€ for windows products. They are usually reselled unused licences from an enterprise licence pool. As an example, I am the IT guy from the local school in my spare time, which we can see as a little company (50 laptops, 1 server, 2 xerox, ...) and we buy MS Office licences for new computers in the school. The microsoft volume licensing scheme delivers in our case usually up to 5 more licences than the bought amount with each purchase, that you may or may not use - do not ask me why. I won't go into details but due to public money and regulations and bla bla we HAVE to buy new licenses and cannot use these free ones. I could easily resell the unused licence keys because I will never be able to use it, and that is precisely what companies like the one you mentioned do.
I do not think it is entirely fully legal, but I do not think it is written anywhere that is not, so ...
Long ago, and with a different version, I had some trouble with a MS Windows license. As it turned out, I had a product that was validly installed via an OEM key that had since expired. It was later disabled by MS because it was being used 'fraudulently' . Also, it could only be used on OEM versions and OEM versions could only use OEM keys.
In my case, I had a valid MSDN key to reactivate it but it was rejected. There were all sorts of unpleasant problems, but only after it went bad and I needed to reactivate it.