Adelino: Yeah, I'm slightly embarrassed myself. Though I never went to
film school this is probably lower than my average for capturing these things on film. I don't have that experience that Scoble has and I went to school as a developer so this is going to take a while to perfect.
Building complex service-oriented solutions requires several architectural considerations including services and contract design, communications security, operations manageability and provisioning, and so on. Add to this, the time-honored issues architectural
teams are mired with—architecting upfront with deployment in mind, ensuring design changes are propagated to code and vice versa, establishing seamless communication between design and development teams and design and operations teams.
Visual Studio 2005 Team Architect Edition addresses exactly these problems at the core with a set of Distributed System Designers that help reduce the complexity of developing and deploying service-oriented applications. A core deliverable of the Dynamic
Systems Initiative (DS), these designers, leveraging the System Definition Model (SDM), allow senior developers and architects to define service-oriented applications that will be configured into systems for deployment. While application architects can visualize
their service-oriented applications, developers can work with the generated code while keeping the code-changes synchronized with the visual design. In addition, the Distributed System Designers can be used to create diagrams or interconnected hosts that represent
the logical structure of a data center for the purpose of communicating important information to the developer about the target deployment environment. The Distributed System Designers can also bind applications to these logical servers and validate them against
the constraints of the application/data center prior to actual deployment.
I was wondering if anyone would catch that. Diane was using our standard automation libraries that we've built for testing Visual Studio. Chetan was demonstrating a newer, in development, approach that translated his actions into calls to the accessibility
apis for playback.
"Some of those offices looked kinda crowded (and hot) with two people in them. Looks like Jeremy had a big fan to keep him cool. Is that the norm around there?"
For some reason Jeremy's office is worse than others. We think it has to do with the placement. But yeah, offices with a lot of computers tend to get pretty hot.
"They should glue the 9 guy on top of the camera and/or mic."
Well, what other reason does Robert have to be walking around the buildings? I think just seeing him is fair warning.
"But then why does it have the same new-line squiggle bug as Word? - I am talking about 2003, not 2005. Is 2003 a rich-text based program? "
No, our editor has been an owner drawn control for a long time. Yes, the squiggles may look the same and are for relatively the same purpose, but I don't believe they share much (if any) code.
"Wow! Touch-based computing. How do you delete stuff? White-out?"
In Developer Division, code deletes you.
"Any chance of making the install faster, why does it take so long anyway? 25mins + (Based on VS 2003)"
I should get a video with the team working on the installer. From what I know VS 2005 should be faster. We now use cab compression to reduce the disk access time required of the install and they've also done a lot of other work including some UI streamlining.
The Express SKU installs should also be much faster due to the reduced footprint of the SKU.
"So you're probably using VS 2K3 to write VS 2K5. But have you used VS 2K5 on any production stuff yet?"
I can't speak for everyone, but most of the developers I know are currently using VS 2005 to develop VS 2005 and the test teams have been using it to test itself for a long time. Dogfooding is big here.
No, Mark is still the lead of the Devdiv Customer Connection team and still my manager. I know his blog has been silent since June, but he has still be hard at work getting other team involved in the community.