Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / csf-dev/CSF.ORM issues and pull requests
#9 - To support multiple framework versions, enable multi-targeting
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#9 - To support multiple framework versions, enable multi-targeting
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#9 - To support multiple framework versions, enable multi-targeting
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#9 - To support multiple framework versions, enable multi-targeting
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#8 - To publish libraries for reuse, they must be made available via NuGet
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, build/deployment
#8 - To publish libraries for reuse, they must be made available via NuGet
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, build/deployment
#8 - To publish libraries for reuse, they must be made available via NuGet
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, build/deployment
#8 - To publish libraries for reuse, they must be made available via NuGet
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, build/deployment
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#7 - To provide summary info, a new README must be written
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement
#6 - To see CI results, build must occur in AppVeyor and Travis
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#6 - To see CI results, build must occur in AppVeyor and Travis
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#6 - To see CI results, build must occur in AppVeyor and Travis
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#6 - To see CI results, build must occur in AppVeyor and Travis
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#6 - To see CI results, build must occur in AppVeyor and Travis
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#6 - To see CI results, build must occur in AppVeyor and Travis
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, build/deployment
#5 - To provide maximum compatibility, decide upon compile targets for the aspects of this project
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, question
#5 - To provide maximum compatibility, decide upon compile targets for the aspects of this project
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, question
#4 - To add support for available APIs, a plan must be devised to support asynchronous database operations
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement
#4 - To add support for available APIs, a plan must be devised to support asynchronous database operations
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement
#4 - To add support for available APIs, a plan must be devised to support asynchronous database operations
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement
#4 - To add support for available APIs, a plan must be devised to support asynchronous database operations
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement
#3 - To simplify the API and integrate with core functionality, rework the transaction-handling to integrate with Transaction Scope
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement, question
#3 - To simplify the API and integrate with core functionality, rework the transaction-handling to integrate with Transaction Scope
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement, question
#3 - To simplify the API and integrate with core functionality, rework the transaction-handling to integrate with Transaction Scope
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement, question
#3 - To simplify the API and integrate with core functionality, rework the transaction-handling to integrate with Transaction Scope
Issue -
State: closed - Opened by craigfowler over 6 years ago
- 1 comment
Labels: enhancement, question
#2 - To remove obsolete logic, types must be deleted and a new major version released
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, breaking
#2 - To remove obsolete logic, types must be deleted and a new major version released
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, breaking
#2 - To remove obsolete logic, types must be deleted and a new major version released
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, breaking
#2 - To remove obsolete logic, types must be deleted and a new major version released
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, breaking
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question
#1 - To formalise functionality & provide a stable platform, the API for ORM operations must be documented
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: enhancement, question