April 2006 - Posts
While I was looking into CAS changes in 2.0 I found some very good news about thread changes in 2.0. In .NET 2.0 both Thread.CurrentPrincipal and the Thread Impersonation token are now propagated amongst threads including ThreadPool.QueueUserWorkItem.
Read More...
Recently after I made my original post titled “PInvoke with 32 and 64 bit”, a developer emailed me. They pointed out that there is an internal structure that dynamically resizes based on the architecture; IntPtr. IntPtr will be size of the native chip
Read More...
One of the big difficulties still remaining in .NET 2.0 is the interoping with native API's which takes in types that have different sizes on 32 and 64 bit machines. For most API's this is not a problem. But for many, including most of the memory API's
Read More...
Just ran accross this site. It's very helpful if you deploy any ClickOnce application http://www.windowsforms.net/FAQs/default.aspx?PageID=1&CategoryID=24&tabindex=2
Read More...
This is my first attempt at cross-posting to multiple blogs. Sorry for the spam.
Read More...
Yet another reason to enable FxCop is it double checks some interop defines (Portability and Interop groups). After enabling FxCop on one of my home brewed interop libraries I was surprised that it complained I had some 64 bit portability problems with
Read More...
I've started experimenting with Code Access Security at home. This derives from my desire to better understand .NET security and my recent fascination with ClickOnce applications. This weekend I learned a hard lesson in security. I have a couple of ClickOnce
Read More...
