Jack Gudenkauf - .Net 3.5 for ISVs
- Posted: Oct 09, 2007 at 12:07 PM
- 16,493 Views
- 8 Comments
Several weeks back James Vastbinder was able to coax Jack Gudenkauf into doing an interview on .NET 3.5 targeted at ISVs. Jack is an Architect on the Base Class Library team and tasked to work with Microsoft’s ISV Partners.
In this interview:
- Jack talks about the BCL team and how they work within the larger Server and Tools business unit.
- An inside view of the new Add-In Model in 3.5, (Its Jack's baby and he's rightly proud).
- The Process ISV should mentally walk through when moving to managed code.
Tools and utilities used by the CLR team.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More posts in this blog
-
MC Chris Rocked the house
-
Jack Gudenkauf - .Net 3.5 for ISVs
-
BlizzCon 08: Sampy and Dan at the show!
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Update: Nevermind, rebooting fixed the problem.
For the love of Ballmer... please stop recording/encoding 16x9 videos with the black bars.
4x3 displays/players will add them if needed and 16x9 displays don't need em and end up adding their own giving a nice ring of black around the video.
EDIT: I thought I found it. After I got it to build, I found that the program is not the one that you demo'd. Just for clairification, I was looking for the crossbow app demo. Maybe I just didn't see the project link.
Now the stuff with integrating winforms controls with WPF, all I can say is: ugh, I'm glad I didn't have to write that. All this interop stuff is hard, messy work that Microsoft doesn't get nearly enough credit for. The Java world just says throw away everything you wrote before but Microsoft always tries to help people come into the new platform bit by bit.
Another thing, which is probably not Jack's area, but I might as well mention it here. You mention in the video that one of the advantages about being able to run GUI plugins in different app-domains is that you can unload the plugin to recover memory and other resources. WHat I want to know is when is .NET going to get the ability to unload assemblies and garbage-collect the memory allocated for the code? I know it's a hard problem, but Java has been able to do this for many years and it should be considered an embarassment that .NET still cannot. While AppDomains serve many purposes, including allowing for code to be unloaded, you often don't need the isolation of an AppDomain and don't want the marshalling overhead of communicating across AppDomains, but you do want to be able to load, execute and then discard code.
http://blogs.msdn.com/clraddins/archive/2007/08/06/appdomain-isolated-wpf-add-ins-jesse-kaplan.aspx
Remove this comment
Remove this thread
close