160 results found

1. Inject ReplyClientFactory from RedisMqServer to MessageHandler<T>

   There's a ReplyClientFactory property on RedisMqServer, which is not used at all. I believe that it should be used to override the MessageHandler<T>.ReplyClientFactory property.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add a new method to IContainerAdapter interface to support Resolving with name parameters

   I am using ServiceStack with Autofac IoC.
   There is code provided for wiring up the AutofacIocAdapter as the default resolver for ServiceStack (instead of Funq).
   There are two method currently exposed on the IContanerAdapter interface which is used to expose wiring.
   It would be useful to expose another method to resolve registered components with named parameters .
   It would be very easy as the underlying IContainer interface already exposes this methed.

   So, something like

   public class AutofacIocAdapter : IContainerAdapter
   {
   private readonly IContainer _container;

       public AutofacIocAdapter(IContainer container)
       {
           _container = container;
       }
   
   
       public T Resolve<T>()
       {
           return _container.Resolve<T>();
       }
   
       public T Resolve<T>(NamedParameter parameter)
       {
           return _container.Resolve<T>(parameter);
       }
   
       public T TryResolve<T>()
       {
           T result;
   
           if (_container.TryResolve<T>(out result))
           {
               return result;
           }
   
           return default(T);
   
       }
   
   }
   

   where public T Resolve<T>(NamedParameter parameter) method would be the new method to expose

   I am using ServiceStack with Autofac IoC.
   There is code provided for wiring up the AutofacIocAdapter as the default resolver for ServiceStack (instead of Funq).
   There are two method currently exposed on the IContanerAdapter interface which is used to expose wiring.
   It would be useful to expose another method to resolve registered components with named parameters .
   It would be very easy as the underlying IContainer interface already exposes this methed.

   So, something like

   public class AutofacIocAdapter : IContainerAdapter
   {
   private readonly IContainer _container;

       public AutofacIocAdapter(IContainer container)
       {
           _container = container;
       }
   
   
       public T Resolve<T>()
       {
           return _container.Resolve<T>();
       }
   
       public

   … more
   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Add convenience links on the API metadata page for parameterless GET requests.

   I would be nice to just click on a link for the GET requests and actually execute the request and see the output. Right now I have to look at the metadata page for the request, copy the url path, and then paste it into browser address tab.

   This probably would not be feasible for POST requests however, unless you want to get fancy with a button or something instead of a link.

   I'm also basically assuming that this would only work for requests with no parameters. Otherwise you'd have to make assumptions of some sort.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Support Calls to .ToString() in SqlExpression Where Clause

   This feature is useful when you need to do STRING related operations on NON STRING types like INT.

   One use case is when you need to do pattern matching (used in searches) on an INT column. That would be great to be able to just write:

   q.Where(x => x.IntColumn.ToString().Contains("123"));

   which should generate the following in SQL Server:

   WHERE cast(IntColumn as VARCHAR) LIKE '%123%'

   Since this feature is not implemented we have to use something like this:

   q.Where("cast(IntColumn as VARCHAR) LIKE '%123%'");

   Which is not that good because it is not strongly typed. And also for that SqlExpression to work, OrmLiteUtils.IllegalSqlFragmentTokens needs to be modified to exclude dangerous keywords like "cast".

   Similar feature in NHibernate: https://nhibernate.jira.com/browse/NH-2563

   This feature is useful when you need to do STRING related operations on NON STRING types like INT.

   One use case is when you need to do pattern matching (used in searches) on an INT column. That would be great to be able to just write:

   q.Where(x => x.IntColumn.ToString().Contains("123"));

   which should generate the following in SQL Server:

   WHERE cast(IntColumn as VARCHAR) LIKE '%123%'

   Since this feature is not implemented we have to use something like this:

   q.Where("cast(IntColumn as VARCHAR) LIKE '%123%'");

   Which is not that good because it is not strongly typed. And also for that SqlExpression to work, OrmLiteUtils.IllegalSqlFragmentTokens… more

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Per-Service Date Format

   Last time I asked it was an all or nothing thing...

   Basically the CMS we have started off with WCF as the default Date format for JSON.

   They then licensed SS and started building new components using SS, and globally (to maintain consistency) kept that crappy unreadable date format.

   So my problem is that I can't globally set ISO as the date format or the entire CMS backend just blows up.

   I would like to be able to attach an attribute to a service method to have it format the dates to ISO on a one-off basis as needed.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Akin to Swagger, please provide built in support for RAML

   RAML (see raml.org) is pretty sweet as a design tool... like Swagger 2.0, you can design your full API and corresponding documentation in the designer tools.

   It would be nice to have ServiceStack support reading RAML generated specs and automagically create the corresponding ServiceStack API with stubbed in methods.

   One of the nice things about RAML is the ability to generate a mock JSON responses and/or status codes from a specified endpoint as directed by the RAML designer tools. This allows it easy for other peer developers (and regression tools) to consume your service although it might still be under development or is incomplete.

   RAML (see raml.org) is pretty sweet as a design tool... like Swagger 2.0, you can design your full API and corresponding documentation in the designer tools.

   It would be nice to have ServiceStack support reading RAML generated specs and automagically create the corresponding ServiceStack API with stubbed in methods.

   One of the nice things about RAML is the ability to generate a mock JSON responses and/or status codes from a specified endpoint as directed by the RAML designer tools. This allows it easy for other peer developers (and regression tools) to consume your service although it might still be under… more

   55 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. ExcludePropertyReferences for Data Contracts

   Currently ExcludePropertyReferences is expecting DeclaringTypeName.DataContractName. Its more helpful if the type is fully qualified.

   for example ; from below Json if we want to exclude :{"Officeaddress.houseaddress.city"}; .

   Json:
   //----------------------------------------------------------------------------
   {"id":"eb26f100-3758-4a19-806b-cd5af44f88a4","data":{"lname":"Talluri","firstname":"RamaNaresh","city":"Atlanta"},"collections":{"houseaddress":[{"id":"126e057d-e91b-42ec-b40d-bdba9c831d64","data":{"city":"CAToronto"}}],"officeaddress":[{"id":"5ff48bd4-bfe2-4721-adf1-3f5cd3b5c736","data":{"city":"USAlpharetta"},"collections":{"houseaddress":[{"id":"aad21efc-2768-4518-a505-71dc8b82ad40","data":{"city":"CA_Downtown"}}]}}]}}
   //----------------------------------------------------------------------------
   Model :
   //----------------------------------------------------------------------------
   [DataContract]
   public class AddressModel : BaseModel
   {
   [DataMember(Name = "id")]
   public System.Guid Id
   {
   get;
   set;
   }

       [DataMember(Name = "data")]
       public virtual BaseAddress Data
       {
           get;
           set;
       }
   
       [DataMember(Name = "collections")]
       public virtual AddressCollection Collections
       {
           get;
           set;
       }
   }
   
   [DataContract]
   public class BaseAddress
   {
   
       [DataMember(Name = "lname")]
       public string LastName
       {
           get;
           set;
       }
       [DataMember(Name = "firstname")]
       public string FirstName
       {
           get;
           set;
       }
       [DataMember(Name = "city")]
       public string City
       {
           get;
           set;
       }
   }
   
   
   [DataContract()]
   public class AddressCollection
   {
   
       [DataMember(Name = "houseaddress")]
       public virtual List<HAdddress> HAdddress{get; set;}
   
   
       [DataMember(Name = "officeaddress")]
       public virtual List<OAdddress> OAdddress { get; set; }
   
   }
   
   
   [DataContract]
   public class HAdddress
   {
       [DataMember(Name = "id")]
       public System.Guid Id
       {
           get;
           set;
       }
   
       [DataMember(Name = "data")]
       public virtual HAddressData Data
       {
           get;
           set;
       }
   }
   
   [DataContract]
   public class OAdddress
   {
       [DataMember(Name = "id")]
       public System.Guid Id
       {
           get;
           set;
       }
   
       [DataMember(Name = "data")]
       public virtual OAddressData Data
       {
           get;
           set;
       }
   
       [DataMember(Name = "collections")]
       public virtual SeAdddress Collection { get; set; }
   }
   
   [DataContract]
   public class HAddressData
   {
       [DataMember(Name = "city")]
       public string City { get; set; }
   }
   
   [DataContract]
   public class OAddressData
   {
   
       [DataMember(Name = "city")]
       public string City { get; set; }
    }
   
   [DataContract]
   public class SeAdddress
   {
       [DataMember(Name = "houseaddress")]
       public virtual List<HAdddress> SECAdddress { get; set; }
   }
   
   [DataContract]
   public class SeAdddress2
   {
   [DataMember(Name = "id")]
       public System.Guid Id
       {
           get;
           set;
       }
   
       [DataMember(Name = "data")]
       public virtual BaseAddress Data
       {
           get;
           set;
       }
   }
   

   [DataContract]
   public class BaseModel
   {
   }

   //-------------------------------------------------------------------------
   object to serialize
   //-------------------------------------------------------------------------
   var aModel = new AddressModel
   {
   Id = Guid.NewGuid(),
   Data = new BaseAddress() {FirstName = "RamaNaresh", LastName = "Talluri", City = "Atlanta"},
   Collections = new AddressCollection()
   {
   HAdddress = new List<HAdddress>()
   {
   new HAdddress() {Id = Guid.NewGuid(), Data = new HAddressData() {City = "CAToronto"}}
   },
   OAdddress = new List<OAdddress>()
   {
   new OAdddress()
   {
   Id = Guid.NewGuid(),
   Data = new OAddressData() {City = "USAlpharetta"},
   Collection = new SeAdddress()
   {
   SECAdddress =
   new List<HAdddress>()
   {
   new HAdddress()
   {
   Id = Guid.NewGuid(),
   Data = new HAddressData() {City = "CA_Downtown"}
   }
   }
   }
   }
   }
   }
   };

   jsScope.ExcludePropertyReferences= new []{"Officeaddress.houseaddress.city"};

   Thanks

   Currently ExcludePropertyReferences is expecting DeclaringTypeName.DataContractName. Its more helpful if the type is fully qualified.

   for example ; from below Json if we want to exclude :{"Officeaddress.houseaddress.city"}; .

   Json:
   //----------------------------------------------------------------------------
   {"id":"eb26f100-3758-4a19-806b-cd5af44f88a4","data":{"lname":"Talluri","firstname":"RamaNaresh","city":"Atlanta"},"collections":{"houseaddress":[{"id":"126e057d-e91b-42ec-b40d-bdba9c831d64","data":{"city":"CAToronto"}}],"officeaddress":[{"id":"5ff48bd4-bfe2-4721-adf1-3f5cd3b5c736","data":{"city":"USAlpharetta"},"collections":{"houseaddress":[{"id":"aad21efc-2768-4518-a505-71dc8b82ad40","data":{"city":"CA_Downtown"}}]}}]}}
   //----------------------------------------------------------------------------
   Model :
   //----------------------------------------------------------------------------
   [DataContract]
   public class AddressModel : BaseModel
   {
   [DataMember(Name = "id")]
   public System.Guid Id
   {
   get;
   set;
   }

       [DataMember(Name = "data")]
       public virtual BaseAddress Data
       {
           get;
           set;
       }
   
       [DataMember(Name = "collections")]
       public virtual AddressCollection Collections
       {
           get;
           set;
       }
   }
   
   [DataContract]
   public class BaseAddress
   {
   
       [DataMember(Name = "lname")]
       public string LastName
       {
           get;
           set;
       }
       [DataMember(Name = "firstname")]
       public string FirstName
       {
           get;
           set;

   … more
   27 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Abstraction for Cassandra and other common NoSQL option

   NoSQL is an important piece of technology nowadays. I would like to see if I could have an abstraction layer for each NoSQL support so that I can switch easily,.

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Allow customization of ModelDefinition in ORM Lite

   I need to be able to customize the ModelDefinition after it is generated by ORM Lite. I propose adding a method to IOrmLiteDialectProvider named CustomizeModelDefinition(ModelDefinition modelDef). In the base dialect providers, there are multiple methods used to create ModelDefinitions. I propose that all of those calls be routed through one method in OrmLiteConfig.GetModelMetadata(this Type modelType). In that method, after the model is created, it would invoke DialectProvider.CustomizeModelDefinition(modelDef). I downloaded and implemented this and tested it. It didn't take long and worked well. I would be happy to share the code.

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Option to maintain references when serializing/deserializing.

    My use-case is serializing compound DTO objects before sending them over the wire. There is no escaping the possibility that multiple references may exist. I can try to hack a solution that maintains references before/after serialization, but I really think this should be included in the serialization process as an option if at all possible.

    There is already an older post on Stack Overflow about this, and I think (hope? ;) others would want the functionality as well.

    http://stackoverflow.com/questions/11644905/serialize-deserialize-complex-type-to-json-with-object-references-and-dictionari)

    I didn't want to bump that, so I'll add my comments here:

    Currently, PCLs are significantly growing in popularity, as cross-platform development (Interoperability and mobility of objects) becomes increasingly important. Because of this trend, more complex object serialization because more important.

    In my particular use-case, I have a transport object that contains some code inside of it to move among logical nodes (intra-process, inter-process, client-server, etc.). This is largely possible due to the shift toward PCLs, and I think I won't be alone in this kind of structure.

    I would use BinaryFormatter if at all possible, but it isn't available in PCLs. Json.NET has problems with PCL implementations, and other serialization implementations I've found don't have the active development that Service Stack does - that's why I bought a license for the serializer in the first place. Active and good!

    I know you have a ton of other features on the boil, but I think maintaining references in any of your serializers (not necessarily Json) would be a huge success in moving toward the PCL world. That's my three cents.

    My use-case is serializing compound DTO objects before sending them over the wire. There is no escaping the possibility that multiple references may exist. I can try to hack a solution that maintains references before/after serialization, but I really think this should be included in the serialization process as an option if at all possible.

    There is already an older post on Stack Overflow about this, and I think (hope? ;) others would want the functionality as well.

    http://stackoverflow.com/questions/11644905/serialize-deserialize-complex-type-to-json-with-object-references-and-dictionari)

    I didn't want to bump that, so I'll add my comments here:

    Currently, PCLs are significantly growing in popularity, as… more

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Add Navigation Properties To POCOs

    Entity Framework currently has navigation properties for foreign keys to other tables. Having this feature in OrmLite would be absolutely amazing.

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Security audits

    I would love to see a security audit on the source code done at major milestones. You don't need to do them on each minor version, but one per year would be ideal.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Pull MiniProfiler out of SS providing OOTB integration

    MiniProfiler would be an external package to streamline the upgrade path. We would be able to use up to date versions of MiniProfiler and its "newer" features (in my case I want to use client side profiling in Razor Views).

    It would be great to maintain the existing "integration" by having OOTB support for SS services, request and response filters profiling.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Appsettings with wildchar get Api

    Possibility to get all the keys via wildchar ...For example retrieve all the items that starts with "widget:" and store them in a dictionary <string, T>

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. A registry of 3rd party plugins, features, etc.

    Host or maintain a list of 3rd party ServiceStack extensions, similar to ngmodules.org for AngularJS, the listing capability of npmjs.org, or http://plugins.telerik.com/ for Telerik AppBuilder.

    The list needs not be actively curated, but a single source where packages are listed and links to download / source code.

    As the user base of ServiceStack grows, people are building more extensions that don't necessarily belong in the core modules, and this type of list would provide a great way of bringing attention to them, outside of hard-to-find NuGet packages.

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Allow filtering of services on metadata page by endpoint

    If you have many services, which you also want to provide via soap and other endpoint types and thus need multiple for each http verb. It would be great to be able to filter the metadata page based on endpoints (JSON, JSV, SOAP, Protobuf, etc.).
    Similare to the already provided filter function or via chechboxes to turn each endpoint on and off.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. When calling services on the same server I would like to bind to the services using named pipes for most efficient inter proces communicati
    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Async PostFileWithRequest

    Please add overload for PostFileWithRequest which is asynchronous in the same way SendAsync is implemented in ServiceClientBase - meaning an overload which accepts success/error Actions and the other which returns Task, or if both are not possible then just the latter.

    This is mainly because in Silverlight sync APIs are not "welcome" which means we have to 'manually' call this API in an async manner.

    Thanks!

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Add feature "Named Type Registrations" to IOC

    IOC container based on convention such as below address

    http://msdn.microsoft.com/en-us/library/dn178463(v=pandp.30).aspx#sec21

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Add persistence support for Couchbase

    This shouldn't be too hard considering you seem to already support memcached..?

    20 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close