Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to extend WCF DataServices and EntityFramework Model using MEF
    primarykey
    data
    text
    <p>I'm using a vanilla WCF DataService class exposing a simple Entity Framework Model. The service is contained in a simple Web Application published to IIS. Nothing fancy, right!</p> <p>I'm trying to build what MSDN describes this way</p> <blockquote> <p><strong>Request and Application Scope</strong><br> Instances of parts created in an MVC app exist in one of two scopes: the request scope or the application scope. By default, part instances that are created during a web request are in a request scope. Instances of parts that are in the same request are shared, so if more than one part imports a given part, all importers receive a reference to the same instance. Each web request has its own scope, so parts created in one request are never used to fill imports in another request. When a request ends, its associated scope is destroyed and any parts created for it are destroyed. Parts that implement an IDisposable object are disposed. This ensures that sensitive resources, such as database connections, are properly closed. Sometimes, you might not want to create a part instance for each request (for example, when you implement an app-wide cache). In these cases, you can force a part to be created in the application scope by applying the ApplicationScoped attribute. Parts in the application scope are always shared by all requests in the app. A part in the application scope may depend on other part in the application scope only for its imports. Parts in the application scope must be careful to be thread-safe.</p> </blockquote> <p>One of the main problems is that I don't know where to create the RequestScope Container. I think the RequestScope Container should be build outside of the DataService class, right?</p> <p>Any help appredicated</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload