Garrett Serack: Open Source Development at Microsoft

View from deep inside Microsoft's Open Source Software Lab

Browse by Tags

Tagged Content List
  • Blog Post: Fixing WebRequest’s desire to throw exceptions instead of returning status

    My pappy always used to tell me “There are three kinds of men: The ones that learn by reading. The few who learn by observation. The rest of ‘em have to pee on the electric fence.” … somedays, I’m surprised how often I get to pee on the damn fence. So, here I am writing...
  • Blog Post: A new full-time member for CoApp

    I’d like to introduce a new member of our team; Tim Rogers.   Tim is a new full time employee at Microsoft who started this week, and as he just found out yesterday (his first day in the office), is going to be working as a full-time test resource for CoApp.   Tim has a [...]
  • Blog Post: Shallow-forking a project

      We’re nearing the point where we’re able to take open source projects and produce happy-shiny packages for them—uh yeah, nearing.  It’s gonna be a couple more weeks shaking out the tools that generate new Visual Studio project files for a given project and wire all that stuff up. The good...
  • Blog Post: We’ve Moved CoApp code hosting to Github

    Just a quick update today—we’ve moved the source repositories for CoApp from Launchpad to Github. While I liked a lot of the things about Launchpad, the website is feeling slower and slower some days, and Bazaar, while offering the features that I like, isn’t getting the attention (and developer resources...
  • Blog Post: Binding Events to .NET 4.0 Tasks instead of Objects (Part 2)

    In my last post, I showed how we’re binding event handlers to the Task after it’s already been started. This of course, is probably not what you want, as it’s possible to lose some events if the task starts up quick enough. So, the CoTask task factory also lets you pass the event listeners as [...]
  • Blog Post: Binding Events to .NET 4.0 Tasks instead of Objects (Part 1)

    During the development of CoApp, I’ve enthusiastically embraced the .NET 4.0 Task Parallel Library (aka, the TPL).  It’s a set of APIs that make developers more productive by significantly simplifying the process of adding parallelism and concurrency to applications. I got religion around this last fall...
  • Blog Post: CoApp “Package Composition”

    (cross-posted from the mailing list) When CoApp packages are installed, they install into a predetermined location based on the package metadata—this ensures that all packages play by the rules, and allow us to use Windows features to support things side-by-side installation of applications (ie, havin...
  • Blog Post: Building the CoApp alpha bits

    The following is the instructions on how to build the current CoApp bits: 0. You need to have the following tools installed in order to build CoApp: Visual Studio 2010 (I’m told that VS 2010 Express will work) Windows SDK 7.0 or higher — http://bit.ly/bOoxJT Windows WDK 7.1 — http:...
  • Blog Post: CoApp in the first 90 days

    (cross-posted from the mailing list ) It has been nearly three months since launching the CoApp project, and in that time I’ve been absolutely amazed at the response that we’ve gotten, and the community folks that have jumped on board. As a matter of fact, it’s been far busier than I had hoped, and was...
  • Blog Post: 1998-The year I built my first Package Management System

    In a couple of weeks the CoApp Design & Development Summit that will take place here at Microsoft, I’ll have 15 or so people from around the world to thrash thru my some of my crazy ideas regarding package management on Windows. Scheduling this even has slowed down discussions on the CoApp mailing...
  • Blog Post: CoApp FAQ: Can you explain how Side-by-side (WinSxS) works?

    (cross-posted from the mailing list ) Windows Side-by-side (WinSxS) technology is a really shiny piece of technology that is not well enough understood, and often misused. This comes from a variety of reasons, one of which is the documentation—while quite excellent—only makes sense if you actually understand...
  • Blog Post: CoApp FAQ: How can I bind to a very specific version of a library?

    (cross-posted from the mailing list ) We had a discussion on the mailing list about maintaining a Symlink to the most recent version of a particular library, and this was of some concern. The installation directory (where libraries and their associated files) are installed has absolutely zero effect...
  • Blog Post: CoApp FAQ: Why demand all code be signed?

    (cross-posted to the mailing list ) I’m answering this in a one-off manner a little too often, so I’ll dump it all here.   Q: What is Code Signing? A: For the long-winded answer, check out Wikipedia’s article on Code Signing . All that aside, it’s a way of attaching a cryptographic signature to...
  • Blog Post: Notes about shared libraries in CoApp

    (cross-posted to the mailing list ) Since I’ve been jumping all around the map on answering questions, I wanted to first jump into the heart of what CoApp really fixes, and we’ll work our way out from there. Libraries (static or dynamic) are the heart and soul of pretty much all software—and open source...
  • Blog Post: The 90 second description on how CoApp packages will get built.

    So, I’ve been taking questions as to how CoApp packages get built. Lemme see if I can sketch out the vision for you, so that you get an idea of where it’s going. This isn’t set in stone, but I’ve actually validated this is a workable solution.   And, before we get too far, let me make this exceedingly...
Page 1 of 1 (15 items)