From 055400864801863106037259f762c6e0810ff284 Mon Sep 17 00:00:00 2001 From: Chris Peterson Date: Thu, 9 May 2024 13:03:41 -0400 Subject: [PATCH 1/2] Adding start ideas for an Entity Framework setup or local text storage per app, common roster language, and an external idea for central Entity Bulk Operations as a service as center of operations which reads in this API POSTs async. Todo - Design a way for locally stored rosters AKA where a roster comes from does not need to be known. Form a common roster language for any Team Builder to POST. Ideas JSON or YAML or even XML. This Team Builder can utilize an Entity Framework POCO database. As any Team Builder app posts to our Team Builder API using the common roster language, a bulk operations Entity can certainly be copied... on all rosters being POSTED by any app that calls this API. Feature 1) Common roster language to POST. Feature 2) A local storage for rosters that connect to this API to POST. Feature 3) A central or local Entity Framework to store rosters per app. Could even be a local text file per app... As long as this API is connected to, it will accept POST using common roster language. Feature 4) An external centralized Entity Framework Service that uses Bulk Operations async to read in all POSTS from any app connected to this API... Which can be the center of operations. --- TeamBuilder/Models/TeamBuilderContext.cs | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/TeamBuilder/Models/TeamBuilderContext.cs b/TeamBuilder/Models/TeamBuilderContext.cs index 862c4e8..560ce49 100644 --- a/TeamBuilder/Models/TeamBuilderContext.cs +++ b/TeamBuilder/Models/TeamBuilderContext.cs @@ -2,6 +2,20 @@ namespace TeamBuilder.Models { + /* + Todo - Design a way for locally stored rosters AKA where a roster comes from does not need to be known. Form a common roster language for any Team Builder to POST. + Ideas JSON or YAML or even XML. + This Team Builder can utilize an Entity Framework POCO database. + As any Team Builder app posts to our Team Builder API using the common roster language, a bulk operations Entity can certainly be copied... + on all rosters being POSTED by any app that calls this API. + + Feature 1) Common roster language to POST. + Feature 2) A local storage for rosters that connect to this API to POST. + Feature 3) A central or local Entity Framework to store rosters per app. Could even be a local text file per app... + As long as this API is connected to, it will accept POST using common roster language. + Feature 4) An external centralized Entity Framework Service that uses Bulk Operations async to read in all POSTS from any app connected to this API... + Which can be the center of operations. + */ public class TeamBuilderContext : DbContext { public TeamBuilderContext(DbContextOptions options) From 5408c68e23936502932d3ba1a9508e52cc38b8a5 Mon Sep 17 00:00:00 2001 From: TeamBuilderApp Date: Sat, 11 May 2024 07:01:24 -0400 Subject: [PATCH 2/2] Package updates. Added nuget.config for Azure Devops pipeline package deployment. Ref: https://github.com/microsoft/artifacts-credprovider/blob/master/helpers/installcredprovider.ps1 https://dev.azure.com/teambuilderapp/TeamBuilder/_artifacts/feed/teambuilderapp/connect "Connect to Dotnet Feed.". --- TeamBuilder/TeamBuilder.csproj | 6 +++--- TeamBuilder/nuget.config | 7 +++++++ 2 files changed, 10 insertions(+), 3 deletions(-) create mode 100644 TeamBuilder/nuget.config diff --git a/TeamBuilder/TeamBuilder.csproj b/TeamBuilder/TeamBuilder.csproj index fe46f44..8ff51e0 100644 --- a/TeamBuilder/TeamBuilder.csproj +++ b/TeamBuilder/TeamBuilder.csproj @@ -6,10 +6,10 @@ enable - + - + @@ -30,7 +30,7 @@ - + diff --git a/TeamBuilder/nuget.config b/TeamBuilder/nuget.config new file mode 100644 index 0000000..05411a6 --- /dev/null +++ b/TeamBuilder/nuget.config @@ -0,0 +1,7 @@ + + + + + + + \ No newline at end of file