Have you looked at the helper method called @HTML.Action("ActionName", "ControllerName")? You can embed those on your _Layout (i.e. master) page as well as other views. It doesn't change the URL and allows you to grab data it its own controller separately from the host page. I use it with good success.
-Brian Hall-
For a website, I personally love http://code.professor-mustard.org/index.htm[^]. There are some "beginner" programming concepts in there, but it's laid out well enough that an experienced programmer from another OO language could navigate around to find the bits they are looking for. It's a one way site where the author remains anonymous (i.e. no blog, forum, or contact area). The other "indispensable" book for me is "C# 4.0 in a Nutshell" by author's Joe & Ben Albahari. These are the same guys who wrote the program LINQPad[^]. It covers the entire gamut of the language and can be a great read through as well as a great desktop reference. Especially for experienced OO developers coming to C#.NET.
-Brian Hall-
"You know you're a geek when..." you dream about doing Google searches and (after a few "Error 404" pages) actually find some interesting articles to read. :-D
Disclaimer: I've been breaking into developing via the C# language for about 7 months now, so take it easy on me. I am writing an add-in to a 3D CAD program called Autodesk Inventor. It has a COM API and they (Autodesk) provide a nice project template to start from which includes the proper references as well as some pre-baked code to get you started. I have been succesfully coding against it for a couple of months now and I have decided to try out the new C# 4.0 language features that just came out with VS 2010. I'm really liking the named and optional parameters, but I digress. When debugging, I start up an Inventor.exe session which, in short, looks to the registry and finds my add-in and loads it. The problem I'm having is actually hitting a breakpoint in my code while debugging. I have gone through several different property settings on the referenced InventorInterop.dll as well as options on debugging (among other trial and error things), none of which seems to work. The only thing that works is when I go back to an earlier .NET framework (i.e. not 4.0). I have tried this on other *sample* add-ins that come with the SDK and the same thing happens. The add-in loads and code gets executed, but the breakpoints don't get hit when targeting the .NET 4.0 framework. Is this a problem with me, the COM interop, or something else altogether? Thanks in advance. -Brian Hall-