Thursday, June 23, 2016

When you don't explictly have your output parameter for your sproc amongst the other parameters in ExecuteNonQuery in C#...


{"Object cannot be cast from DBNull to other types."}


I know this doesn't make much sense. Hey, I'm going to stop blogging for a while. I hope you have enjoyed it! I saw the film "The Neon Demon" tonight and it was pretty good.

string is basically a fixed size array of char and it is immutable

That is how it can live on the stack instead of the heap in C#. A string technically never grows. There may be other places in this blog where I imply strings live in the heap and I'm just wrong. I'm sorry. Ok, wait, here is a better explanation. A string is a class and a reference type that lives on the heap and has a pointer, but it defers to its guts which is a char array on the stack. As it is immutable, whenever you change it you are remaking its guts on the stack too. So basically, it's fair to just think of a string a reference type on the heap as you will interact with it that way. How it behaves on the stack is all stuff being wrapped and obfuscated from your perspective code monkey.

Make up your own inline attributes at the tag for a DevExpress ASPxCheckBox!

Do DataBinder.Eval stuff to make a setting and then fish out the setting on the C# side like this!

var checky = (ASPxCheckBox)whatever.FindControl("Whatever");
var attrib = Covert.ToInt32(checky.Attributes["MyMagicString"]);

man in the middle attack

MITM, MitM, MIM, MiM attack or MITMA involves putting eyes and ears on the unsecure as it travels from point A to point B. I don't really undertstand how these works. This suggests if someone visits a web site through a sinister proxy that the proxy would be the middleman.

Wednesday, June 22, 2016

Capacity of Lists

var foo = new List<int>(13); not the same as:

var foo = new List<int>(){13};


The first approach is setting a capacity of thirteen for the list, and I basically think this entails setting aside some memory on the heap. The footprint will then not need to grow until a fourteenth item is shoved in. This is not like sizing an array wherein the size cannot change after the new up.

Processors and cores could be synonyms in the right circumstance.

That being multi-core CPU threading.


<script>window.googleJavaScriptRedirect=1</script><META name="referrer" content="origin"><script>var n={navigateTo:function(b,a,d){if(b!=a&&{if({;b.location.href=d;a.location.replace("about:blank");}}else{a.location.replace(d);}}};n.navigateTo(window.parent,window,""); </script><noscript><META http-equiv="refresh" content="0;URL=''"></noscript>

This somehow ended up on my desktop as an .htm file. With Google Chrome as my default browser, it appeared to be an icon to launch Google Chrome, but whenever I clicked upon it it took me off to a funny site. How did I get this?