Blog.Start



I have my very own Blog at last! Who am I and what do I do? Let me introduce myself…


I am a solutions architect working in the .Net Enterprise Architecture Team at Microsoft here in sunny Redmond. I focus on the architectural issues surrounding smart client applications and as part of my job I get to work with some of Microsoft’s enterprise customers and help them architect and develop their smart client applications. I also get to work with the product teams who are building the next generation of Microsoft stuff and help to ensure that it’s ready for the big time. So, I am in the cool position of being able to write code for real world applications and I get to play with all the new stuff too!


So what can you expect from my Blog in the coming weeks and months? Well, expect lots of inane waffle on smart clients – things like how to make them work offline, how to deal with caching data, how to deal with concurrency, how to manage deployment, how to make the UI cool, etc.


And obviously there will be lots of stuff about Lord of the Rings – only 12 days to go, not that I’m counting or anything…


 

Comments (5)

  1. Really looking forward to reading your stuff, ‘Smart Clients’ (in whatever form) certainly seem like a logical step (I keep noticing the drift from ‘traditional’ windows based applications to a more connected model)…hmm…could be interesting.

  2. Wallym says:

    I’m not owrthy, I’m not worthy…………

    Wally

  3. We are about 3 months away from going live with our NTD application. The app will be ‘deployed’ from our web server, over the WAN, to numerous clients. The app is ‘started’ via a launcherstub exe that does an Assembly.LoadFrom pointing to the url on our web server (where all the dlls reside). The exe will be distributed to all of our clients.

    I’d like to learn more on how to prevent unauthorized users from loading our dlls. In other words, anyone that gets a copy of the launcherstub, or discovers our external url, has access to our dlls and, in essence, our application. A client that we send the exe to is authorized. Anyone else who gets a copy of the exe is not authorized. How does one prevent this?