CODEWITHSUNDEEP
xamarinxamarin.forms
Janice_Feb_1998
Janice_Feb_1998

Reputation: 23

Should I use dependency injection to bring in a class with constants into my Xamarin Forms application or is there a better way?

I have a class containing constants:

namespace Test.AppService
{
    public static class Const
    {
        public const bool Tmr = false;
        public const int Pti = 10;
        ...

I was wondering if this would be a good candidate for dependency injection or would it be better to leave it as it is and just add using for Test.AppService into every page? Would appreciate advice on this.

Upvotes: 0

Views: 157

Answers (1)

user3912137
user3912137

Reputation: 36

Reading your comment about needing to use a different set of constants if that is something you see happening then Dependency injection makes sense. For example if you are using different environments like DEV, QA, Release comes to mind.

You would need to declare an interface with all your public fields. Implement that Interface in different classes with all the possible different scenarios. Then you can register your interface and the class with your desired set of values that you would be able to swap as needed.

For example:

public interface IConfiguration
{
    public string ConnectionString {get;} 
}

  public class QaValues : IConfiguration
    {
        public string ConnectionString 
        {   get 
           { 
            return "qaconnection"; 
           }
         }
    }

 public class ReleaseValues : IConfiguration
        {
            public string ConnectionString 
            {   get 
               { 
                return "releaseconnection"; 
               }
             }
        }

DependencyService.Register<IConfiguration,QaValues>();

Upvotes: 1

Related Questions