使用 Oslo 和 M 有什么优势？您何时会使用它？
在参加了 Oslo/MI 的演讲后，我有点想了解使用它相对于现有方法的优势以及它在什么情况下有用。
我知道它很新，并非所有细节都已发布等，但有人可以给我一些优势以及您何时可以使用它吗？
谢谢，
亚历克斯
After attending a talk on Oslo/M I am struggling a bit to see the advantages of using it over existing methods and in what situation it would be useful.
I know its quite new and not all details have been released etc but can some one give me some advantages and when you might use it?
Thanks,
Alex
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这个问题似乎有您正在寻找的答案：
模型驱动开发有什么好处？
Erik Wynne 有一个不错的博客-关于此主题的帖子：
奥斯陆 == 42
他还链接到 MSDN 上的一篇文章，该文章包含一些有趣的想法：
为什么我们需要奥斯陆？
This questions seems to have the answer you're looking for:
What is model driven development good for?
Erik Wynne has a nice blog-post on this topic:
Oslo == 42
He also links to a post on MSDN, that contains some interesting thoughts:
Why do we need Oslo?
我还没有玩过 Oslo alpha 位，但我表面上的理解是：
尝试让开发人员更容易地以对他们所工作的领域有意义的方式表达和存储他们的想法 - 即领域建模。
尝试使这些存储的想法在程序执行期间可访问。
因此，更多的趋势是声明性逻辑而不是过程性逻辑。 这似乎就是发展世界的发展方向。 我是个老顽固，远不相信。
但我们不能继续像埃及金字塔那样开发软件，数以百万计的砖块堆叠在一起，没有结构完整性，只有蛮力和成千上万的奴隶。 所以我们需要这些新想法。
I haven't played with the Oslo alpha bits, but my understanding on a superficial level is:
Trying to make it easier for developers to express and store their ideas in ways that make sense for the domain they are working in – i.e. domain modelling.
Trying to make these stored ideas accessible during program execution.
So yet more of the trend towards declarative rather than procedural logic. That seems to be the way the development world is moving. I'm an old fogey, and far from convinced.
But we can't continue making software like an Egyptian pyramid, with millions of bricks piled on top of each other and no structural integrity, just brute force and thousands of slaves. So we need these new ideas.
模型共享也将变得普遍，特别是当 Oslo 存储库可以托管在云中的 SQL Data Services 中时。 模型互操作性是游戏的名称。
奥斯陆有一些意想不到的用途，这些用途将会变得普遍，但最初我知道它们的目的是支持想要创建 Microsoft CRM 和 Sharepoint 等应用程序的开发人员。 这些系统是数据驱动的，具体到用户界面布局。 对于某些类型的系统来说，这是一种有效且高效的方法，并提供了非常可扩展和可维护的体系结构。
有关更多信息，请参阅我关于奥斯陆的文章：
http://dvanderboom.wordpress.com/2009/01 /17/为什么奥斯陆很重要/
Sharing of models will also become common, especially once the Oslo repository can be hosted in SQL Data Services in the cloud. Model interoperability is the name of the game.
Oslo has some unintended uses that will become common, but originally I know they were aiming at supporting developers who wanted to create applications like Microsoft CRM and Sharepoint. These systems are data-driven, down to the user interface layouts. It's an effective and productive approach for certain kinds of systems, and provides a very extensible and maintainable architecture.
See my article on Oslo for more information:
http://dvanderboom.wordpress.com/2009/01/17/why-oslo-is-important/
多思考一下这个问题，在阅读了 Qdoom 和 RoadWarrior 发布的文章后，我可以看到 Oslo 正在帮助共享，
好吧，您可以共享一个带有 xml 和 xml 之类的模型。 xsd 但 Oslo 可以让它变得更容易，因为看起来您可以从中生成类和数据库，同时将模型存储在中央存储库中。
也许以后人们也会出售常见场景的模型。
Thinking about this a bit more and after reading the articles posted by Qdoom and RoadWarrior I can see Oslo aiding sharing,
Okay you can share a model with something like xml & xsd but Oslo could make it easier as it looks like you can generate classes and your database from them whilst storing the model in a central repository.
Perhaps later on people will sell models for common scenarios as well.