Robert McLaws: FunWithCoding.NET

Public Shared Function BrainDump(ByVal dotNet As String) As [Value]

  • Getting an Assembly's Public Key the Programmatic way

    I have been struggling with the dumbest problem all day. I have been working with extending the XHEO|Licensing system with a new licensing limit for a new product that I'm working on. Basically, it limits the assembly to be used only by a specific calling assembly. Anyways, I was looking for a way to get the public key and public key token of an assembly programmatically, and after some hunting through the System.Reflection namespace, I found it. It really sucks though, because I went through the MSDN docs for the AssemblyName.GetPublicKeyToken, and it had an example of almost exactly what I needed The problem is, it didn't work

  • .NET App in CRN Magazine

    I'm flipping through this weeks issue of CRN Magazine, and I see the first mention of a .NET application. The only problem is, it's in the “Hacker Tracker” callout of the Security section. It seems that DotNetNuke had 2 vulnerabilities that allowed hackers to access files located outside teh web directory, as well as an XSS attack could allow user data to be stolen. It was skocking to me to even see a .NET community app mentioned in this mag, but here it is. Hopefully the DNN team got the problem solved. Hopefully I'll see some better .NET news in there in the future.

  • From The 'Wouldn't It Be Great' Files

    Woudln't it be great if Orkut and Plaxo teamed up, so my Orkut friends automagically showed up in my Outlook contacts? That would be frickin swell. Would save me a buttload of time updating my Outlook contacts from my Orkut profile.

  • Optional Parameters in SQL Stored Procedures

    Want to create a stored procedure that searches for specific, but optional, values? I had to do it today for a web project I'm working on (I hate not being able to talk about projects I'm working on) and Terry Denham, the SQL Guru without a blog, came to my rescue yet again. Because the WHERE clause has secluded OR statements buttressed by a "trueism" (Terry's term) of 1 = 1 (does anyone know of a case where one DOESN'T equal one?), the statement will always execute, even if you don't pass anything in. Pretty cool, huh? Thanks Terry! Saved my butt again.

  • PatchDayReview Massive Update

    Over the past few months, I let PatchDayReview.com get way too far behind. It took me nearly 7 hours to update, but the site is now current with all known security updates through this Tuesday. One change of note is that I am no longer allowing comments on bulletins themselves. If you want to comment on a specific patch, there is a link to that bulletin's forum on the PatchDayReview Forums. If you'd like to discuss patches, please do it there. At any rate, sorry to kill your aggregators, but most of you subscribe to Scoble, so you're used to it by now.

  • You Gotta Rip It Off Like A Band-Aid

    Mike Kolitz says that MS should take the 16-bit subsystems out of Longhorn. I agree completely. Chris Anderson had a different opinion at PDC about this, but I still don't agree with his position. Microsoft needs to not enable the crap of yesterday in the OS of tomorrow. Break stuff if you have to. Put VPC in Longhorn and disable it by default. I can understand leaving the 32-bit native stuff in there, but the 16-bit stuff too? Come on. Move forward, and don't look back.