Cool ScriptManager stuff I missed...
So the last week or so I have been doing some heavy handed UpdatePanel development (stuff where I needed to fix an existing form that needs help to support an UpdatePanel or stuff where I needed to do something special while the page was posting back asyncronously).
In the midst I discovered some cool mechanisms that I missed!
For instance you can determine whether the current request is an async request by doing something like this:
1: ScriptManager sm = ScriptManager.GetCurrent(Page);
2: if (sm != null && sm.IsInAsyncPostBack)
Script#: Events/Delegates in an Atlas/MS Ajax style script
ReSharper 4.0 Beta!
I hadn’t seen this mentioned anywhere else. ReSharper 4.0’s Beta has now been released. This is by far my favorite tool in my arsenal. I find how good of a C# programmer I really am when I have to develop without it. The latest version has been updated for C# 3.0 (VS 2008 version). I could copy the rest of the feature list, but you can go read yourself. I have been using the EAP bits since right before the Beta Release Candidate and it appears to be really solid with the last couple of drops.
Papa to write Silverlight2 book
My buddy JP (John Papa) is writing a Silverlight2 book. See his blog here and here for more info. JP is known for his DataPoints column in MSDN magazine (and he is an MV, a former co-worker, and former co-blogger... SO, I read his blog). I found this out a day after I visited the Manning site and purchased to EAP Silverlight2 books. I wish I had known I would have seen what I could do to purchase an early release of JP’s book. Needless to say I expect John’s book to be really good. I know that...
Silverlight2 Programming: The Designer Rule
I’m starting a new series on Silverlight2. I am currently building a little SL2 prototype, and as I am learning things I thought I would write them down here. The first rule deals with working with Designers. It is stated as such. "Prefer XAML code to CLR/DLR code when it comes building interfaces" Note the word "prefer" here. That word means "usually", "normally", or "unless there is an exception." This is best explained by some C# code I saw the other day. It looked something like this: ...
I want to write today about the 300lb Gorilla that none of us really wants to talk about. I'm talking about the people we use to find new jobs. As you may be aware I closed down IntraDynamics, LLC (well, I have greatly curtailed my company's offerings),and got a new job (at Answers Systems, Inc.)
I was "exchanging notes" with my new boss regarding the process and discovered some things (none of this is surprising, but you may want to think about it next time you are pursuing a new job).
I had two recruiters that were aware of my interview...
Composition vs. Inheritance...
[I really should stay out of these discussions... I really should, but I can’t resist.] The other day I saw an article on Composition over Inheritance (I forget where I saw it). The article did a good job of explaining what "composition" is. This is my simplistic understanding (which means that someone will probably come in and tell me I have it ALL wrong... what else is new?): "composition" means essentially wrapping objects instead of direct inheritance (so instead of inheriting from X you instead have a private instance of X in your class that you use, but you...