endpoint.tv - The Road to "Oslo"
- Posted: Aug 20, 2008 at 8:23 AM
- 49,736 Views
- 8 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- High Quality WMV (PC, Xbox, MCE)
- MP3 (Audio only)
- MP4 (iPod, Zune HD)
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Microsoft's "Oslo" project aims at creating a unified platform for model-based, service-oriented applications. This new approach will affect the next versions of several products and technologies, including the Microsoft .NET Framework, Microsoft Visual
Studio, Microsoft BizTalk Server, Microsoft System Center, and more. Although many details of "Oslo" won't be public until later in 2008, this session provides an overview of what Microsoft has revealed so far. Along with a description of the problems it addresses,
the session includes a look at several new "Oslo" technologies, including a general-purpose modeling language, role-specific modeling tools, a shared model repository, and a distributed service bus. With David Chappell and Ron Jacobs.
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.
Follow the Discussion
Yet another service / model / language / tool
I will have to see what they are saying....
I recently did some stuff with the service factory and found that was less than I hoped for.
it did not help with several key issues in defining a service set as it required model chnages to target ASMX or WCF and had a number of anoying bugs.
1) sounds like some of this is the same ideas that we first saw in VS 2005 Team Foundation versions of VS.
2) given the tools in TF and given the seperate tools in Expression and now this how many tools might a dev wind up using?
3) seems like I recall some work that has been done to try and make apps based on design patterns but I have not seen it in the main stream.
I recall with the VS 2005 wave a lot of talk about "Software factories" but I have not heard this term used in the last year or two.
so given 1,2 and 3 and the WF and WCF bits and all the rest I am not so sure we are ready for another wave just yet, or are we?
I really like the idea of using tools to build parts of a system so that I can spend my time on the more creative parts and the things that the tools can't do.
but I do not want to see more SKU's of more apps to work with and I wish that even now most of the VS TF stuff was in VS Pro
(sans the server)
for example VS Pro does not get Code Profiling ... but VS TF sku's get it...
I do not like going between expression and VS to work on SIlverlight and WPF apps...
so I'd really like to see work done in the next wave of VS and tools to work on letting the DEV with VS Pro decide what tools he will use inside of VS Pro w/o having to jump thru hoops.
in many cases (like me) one dev has to cover the *WHOLE LIFE CYCLE*
sure in a large corp. setup therre may be the assortment of different folks doing different bits but I think a lot of folks are more like me where even if you work in a large corp. you need to do a lot of things to get it done. and you can't really explain it to upper mangers to get them to buy all the tools you could use.
cause then they figure the project is to big and turn it over to a bid for a team.
when you can do it w/o the tools but work harder.
but if you had the tools you could do more and look better.
Ok long winded but a valid concern I think.
Not sure what that meant? I hope you realize I write a ton of code and sometimes have to hold off on the videos till I get some work done...
or if I got it worong then tell me what you meant?
Even if you know your project will be "multiplied by 0" with 99% probability it still more "fun" than "work".
"Customers" are boring and can (will, actually) ruin any good intention and enthusiasm.
Ok, the way your reply was written I thought you were saying someting to me about my first comments.... you were really speaking to the topic more than to me. Got It.
yeah, like what I posted, MSFT has built a ton of tools but sometimes I think some of that engergy gets scattered and does not reach the rank and file dev. I'd really like to see a bunch of the teams spend some time on putting all this back into the basic VS V-Next as part of the standard and Pro SKU's and not a "flea market" of 101 different tools.
The possibilities are endless but in the end this, like VSTF, will have its success depend on what general managers in all business contexts need. A not too demanding WYSIWYG that gives them the basic overview and data they need will make them buy and install this. They don't want to have to model anything themselves, they want it ready to use for general repository purposes (business processes, services repository, template and webparts repositories, "whatnot" repositories). Hooking this system into Government strategies like COBIT or anything else they recognize, would probably help immensely.
All developer benefits and possible productivity increase are usually in the category "nice to have". I am intrigued with what they might improve within WCF and WFF though...
I'm sure it's good stuff, but it comes close on the heels of WCF which (it seems to me) has an extraordinarily low adoption rate...
Remove this comment
Remove this thread
close