Try the nerd dinner tutorial. It's the "Hello World" for ASP.NET MVC. It was written with MVC 1.0, but should still work nicely. It's how I learned, and the concepts are really nice and clear. Also, Nerd Dinner is maintained at codeplex.com, where you can, after taking the tutorial, take a look at how the enhancements since MVC 1 have come into play. The Nerd Dinner tutorial can be found here: http://aspnetmvcbook.s3.amazonaws.com/aspnetmvc-nerdinner_v1.pdf[^] You should be able to complete it within a day or two and have a great foundation for being MVC ready.

Way to use the past to close off the future! Not that IE is the future, but that this is a general problem in the technology field. We tend to impose our human frailties on bits and bytes. We either applaud or shun based on the inequalities of the past. How many great technologies have been shuttered because we as a community were being loyalists? Software is exactly what it is: software. It has no past. It's honest and speaks for itself. If it's useful, use it. If not, then don't. But you can't pre-judge it based on conjecture and past bugs/business practices/etc. We close off possibilities when we close our minds.

"ctrl alt delete"

You might take a look at VistaDB too... It's compatible with SQL Server, supports multi-threading concurency, is completely written in managed code, and has an excellent .NET provider. Works with isolated storage and reduced permissions as well, which is a plus for portable apps. Linq support, however, seems to be lacking, but I believe it's a planned feature. Plus, the db engine is less than a 1 MB... www.vistadb.net. ~myker

I wish to prevent AutoPlay from happening when my .NET application is running. According to MSDN (http://msdn.microsoft.com/msdnmag/issues/01/11/autoplay/default.aspx[^], there are two methods for accomplishing this: 1) Handle the "QueryCancelAutoplay" windows message. This only works when your application is in the foreground and activated. 2) Implement the IQueryCancelAutoPlay COM interface and register with the ROT (Running Object Table) I found an article for the first method at http://www.experts-exchange.com/Programming/Programming_Languages/Dot_Net/Q_20695207.html[^]. However, my application isn't always in the foreground. Therefore, I am left with option 2. The big question I have is, how do I implement the IQueryCancelAutoPlay COM interface and register it at runtime with the ROT using C#? ~mykey What do you get when the devil goes bald? Hell Toupee. :laugh: