Brandon: Why does CableOne suck so much?

---

Seriously? I feel like I'm in the dark ages out here. The cable TV in Humboldt Kansas is more advanced than what they have here.

Maybe Qwest will do a fiber rollout like Verzion did with FIOS. I know it will never happen, but whatever. I can dream I guess.

Also, where does my $150 a month go? At least the internet rarely goes down, and my IP addy is more or less static. Aside from the throttling they do, it could be worse I guess. Speeds kinda blow though, but the DSL is worse in my area.

Anyway, I just wanted to rant a little. Whats sad is I don't even have a HDTV yet. I'm just griping about the lack of On Demand PPV or anything like that.

Also, whats with the 2 PPV channels of movies and the 20 PPV channels of porn? I mean, FFS.

In pain: Due to wisdom teeth extraction.
Grumpy: Due to the pain.


Tags (beta): cable, cableone, rant, tv

Comments (1)

Brandon: Obfuscation

---

I hate obfusaction.

What I am speaking of, of course, is having to obfuscate compiled .NET code so that someone cannot simply reverse engineer it using reflection or some such nonsense.

At work we use a package called Xenocode Postbuild 2007. It is quite improved from the 2006 version, but it still has some annoying issues.

For example:
.NET 2.0 has a XMLSerializer class built in. What this does is take data out of an object and represents it as XML. It makes saving the contents and state of an object quite easy. However, to do this, it (the .NET runtime) creates a new assembly (basically a .NET dll) on the fly. Now, when you obfuscate a program, it takes the variable names and makes them full of random characters, so something like "Name" would end up being "x9038242ndo3412f". Thats all fine and good, but it ends up confusing the generated XMLSerializer assembly sometimes.

And don't get me started on the mess it makes of trying to use reflection. You might as well not even try to protect your code if you are going to use reflection on it.
(Reflection is a way of dynamically loading .NET assemblies at runtime. Think of plugins, thats sort of the idea, but its much more complex than that).

Anyway, code that works fine in a development environment may not work at all if it is obfuscated.

But, how else can you protect your code.



Code: monkey need caffene
Post: is far too nerdy for most.


Tags (beta): code, .net, obfuscation, rant, xml

Comments (1)