Question

备忘录认为,你在本质上是迫切的,探讨你们可以获得哪些数据。在你与2008年美国犯罪率挂钩之后,在你分发申请时发生了什么变化? 你们是否遇到过错? 开发商是否有责任处理这些错误?
Also, does this put the responsibility into the type provider s hands?

Currently when you download a .NET assembly, you know it will never change until you (manually or through a service) explicitly update it. Compile errors from evolving types must be resolved, but you can always hold off the upgrade until you re ready for the change. With type providers, do you have to program more cautiously against them?

Answer 1

对图形变化的反应是提供商的责任,但仅在开发时间。一旦您提出申请,它就利用该类型提供商汇编,并在汇编时使用目前的图表。

When you re using type provider from Visual Studio, it can monitor the schema changes and notify the Visual Studio IDE that there has been a change in the schema. I wrote a XML type provider example that does this, so when you change the schema (XML file used as an example), you ll immediately get errors in VS. I did a video demonstration of this (around 19:40).

Once you compile your program, the type provider generates code that should be used in the compiled form (and the type provider is not used at runtime). This means that if the schema changes at runtime, you can t do anything about it (the developer needs to react). If the schema change is backwards-compatible (i.e. add new columns to a DB table), then your program may still work fine though.

友情链接