EF context is implementation of unit-of-work pattern, it is not repository pattern.
> d) Do I need to dispose the the context on closing the window? Not only on that. you should create and dispose context for every action you do with a database: insert, delete, update, query etc. > 3. As long the user does not explicit reload the data I am working in a > connected mode You don't have to be always connected for any reason. On 25 March 2016 at 09:18, Jiří Činčura <j...@cincura.net> wrote: >> a) Is the method described above considered as good practice? > > From what you've written, yes. > >> b) Basically it is a connected Context until the user refreshes the data. >> In >> this case the context is recreated. > > No problem with that. > >> c) In order to manage multiuser environment, do I need to work generally >> with disconnected entities? > > No, you don't have to. > >> d) Do I need to dispose the the context on closing the window? > > Yes, you should. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 > _______________________________________________ > Firebird-net-provider mailing list > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
