appfabric-beta-2 | 易学教程

AppFabric Caching - What are its serialization and deserialization requirements for an object?

阅读更多关于 AppFabric Caching - What are its serialization and deserialization requirements for an object?

问题 Problem: When caching an instance of a class and immediately getting it back out of cache, i get the object back (its not null), but all of its properties / fields are null or defaults. _cacheHelper.PutInCache("testModuleControlInfoOne", mci); //mci has populated fields var mciFromCacheOne = _cacheHelper.GetFromCache("testModuleControlInfoOne"); //mciFromCacheOne now has null or default fields So I suspect the way the object is structured is the problem and AppFabric is not serializing the

AppFabric Cache - An existing connection was forcibly closed by the remote host

阅读更多关于 AppFabric Cache - An existing connection was forcibly closed by the remote host

问题 I'm trying to get AppFabric cache up and running on my local development environment. I have Windows Server AppFabric Beta 2 Refresh installed, and the cache cluster and host configured and started running on Windows 7 64-bit. I'm running my MVC2 website in a local IIS website under a v4.0 app pool in integrated mode. HostName : CachePort Service Name Service Status Version Info -------------------- ------------ -------------- ------------ SN-3TQHQL1:22233 AppFabricCachingService UP 1 [1,1][1

AppFabric Caching - Can I specify serialization style used for all objects?

阅读更多关于 AppFabric Caching - Can I specify serialization style used for all objects?

问题 An object which implements some custom serialization can be serialized and deserialized to different formats, for example to Xml or byte[]. I have run into a problem where when I put to cache, AppFabric runs the IXmlSerializable implementation on a class when I would rather force it to go with binary. AppFabric Caching - What are its serialization and deserialization requirements for an object? Can I configure this? (At the moment the workaround is to serialize the object programatically to a

Should a Repository return IEnumerable<T> , IQueryable<T> or List<T>?

阅读更多关于 Should a Repository return IEnumerable , IQueryable or List?

I'd like to make my application as flexible as possible, but not dig myself into a hole by making my Interface too specific. What is the best object type for a repository? IEnumerable, IQueryable, or List? The technologies I'm considering using are Azure App Fabric Caching Entity Framework 4.1 Possibly Windows Server AppFabric I would say build your DAL using IQueryable, and pass it around, make sure your object contects lifetime is the request. This way you will get benefit of delayed execution, but are exposed to the risk of inefficient querying of database. Then make sure you performance

Should a Repository return IEnumerable<T> , IQueryable<T> or List<T>?

阅读更多关于 Should a Repository return IEnumerable , IQueryable or List?

问题 I'd like to make my application as flexible as possible, but not dig myself into a hole by making my Interface too specific. What is the best object type for a repository? IEnumerable, IQueryable, or List? The technologies I'm considering using are Azure App Fabric Caching Entity Framework 4.1 Possibly Windows Server AppFabric 回答1: I would say build your DAL using IQueryable, and pass it around, make sure your object contects lifetime is the request. This way you will get benefit of delayed