Series of four web casts on the smart client sample app, Issue Vission.
Microsoft has built a network of Windows XP Honey Pots. These XP boxes are running as Virtual Machines. The network is being used for security research.
On a recent project I had a choice between using Web Services and Remoting. I chose Web Services but I think it is interesting to understand why. First .NET Remoting is a good technology for interprocess communication when developing purely in the .NET environment. Next, .NET Remoting is very fast when serializing binary data over TCP. Remoting is also a good choice when you are operating on an internal LAN.
Open Source .NET Smart Client RSS aggregator.
There are many great topics of debate in software development. DataSets Vs. Objects, Smart Clients Vs. Web Apps, and Stored Procs Vs. Dynamic SQL. Many have argued that writing stored procedures is rigid and doesn't allow for an easy way to build detailed where clauses. Furthermore, SQL Server 2000 caches execution plans so in theory SQL Statements should be optimized if used often. Finally, .NET allows for parameterized queries helping to protect dynamic queries from SQL Interjection.
This weekend I decided to do a little reading and downloaded "Improving .NET Application Performance and Scalability" at http://msdn.microsoft.com/practices/EngPrac/default.aspx?pull=/library/en-us/dnpag/html/scalenet.asp. This is a really good guide and provides you with theory, checklists, and how to's. Anyway, one of the major themes was do not wait until an application is deployed to begin perforance tuning. Instead the authors recommend that performance tuning should be part of the desig