You might also be able to instantiate the .NET DataStores' names (strings) but that goes a bit too deep into C# reflection

Thanks! I think thats something I'm looking for. Im almost able to implement it. This is what I have so far



using (var Oracleconnection = new ODataContext(connectionString))

{

var dataStores = new List<IDataStoreBase>

{

new DataStore<DWOne>(Oracleconnection),

new DataStore<DWTwo>(Oracleconnection)



};



for (int i = 0; i < dataStores.Count; i++)

{

ExportDataStore x = new ExportDataStore();

int threadIdent = i;



Thread myThread = new Thread(() => x.ExportData(threadIdent, dataStores[threadIdent]));

myThread.Start();

threads[i] = myThread;

}



foreach (var thread in threads)

{

thread.Join();

}

}



public void ExportData(int id, IDataStoreBase dataStore)

{

int row = dataStore.Retrieve();

Console.WriteLine("ThreadId: " + id + " Row: " + row);

}



DWOne Works and Retrieves perfectly fine but for DWtwo I get this error when calling the retrieve "Object reference not set to an instance of an object." Im going to keep experimenting because I feel like Im close but can you see anything that stands out that could cause this exception?



Thanks,

Saul

Hi Francisco,

Thanks again for your response. Everything is making sense and what needs to be done to resolve my issue except the "var app = builder.Build();" line. I'm confused what it does and how to implement it. I never used that line in my code. I was doing more research online and it seems I need something called a IApplicationBuilder. I'm not sure if this piece of information is relevant but im only using a console app right not and I have a regular Main(string[] args).



I saw I can do something like -

public void Configure(IApplicationBuilder app, IHostingEnvironment env) { app.UseDataWindow(); }

but I am not sure how to call this function (what to use for the app and env parameters) from my Main(string[] args). Am I going about this the wrong way?



And is this the only way to register the classes with the DataWindow attribute?



Thanks for your time,

Saul

Hi Saul, I thought you were working with a ASP.NET Core API, not on a Console App, my apologies. I believe it's not possible to use the non-generic .NET DataStore outside of a ASP.NET Core API project, but I'll ask around and let you know what I find out. In the meantime you'll have to work with the generic version. May I ask what is it you're trying to accomplish? To see if it can be done in some other way.

Regards - Francisco

No Problem, Let me know if you find out! I'll try my best to explain what I am trying to accomplish. I hope this doesn't format weird..



I have 10 different DataStores, my goal is to create 10 Threads - one for each DataStore. I want to create these threads in a loop and call a function, I'll call it ExportData(DataStore datastore).



My original idea was something like this

string[] datastoreAttributeNames = {"dw1Attribute", "dw2Attribute"};

for (int i = 0; i < DatastoreAttributeNames.Count; i++)

{

var datastore = new DataStore(DatastoreAttributeNames[i], Oracleconnection);

Thread myThread = new Thread(() => ExportData(datastore));

myThread.Start();

}



So i guess how can I pass different DataStores each increment of the loop. Now I am thinking maybe get an array of DataStores - Datastore[] ARGdataStore = new DataStore[10]; - but I'm not sure how i could add different datastores to that array. If I can somehow call ARGdataStore[0] and that be DW1 and then call ARGdataStore[1] and that be DW2 i think my problem would be solved.



Right now my code is chunky and repetitive because I have to create each thread manually and create a new ExportData(DataStore datastore) function for each DataWindow - even though every ExportData function has the same code. I'll use two datastores as an example. These are the function definitions. ExportData01(DataStore<DWone> datastore), ExportData02(DataStore<DWtwo> datastore)



{

var datastore01 = new DataStore<DWone>(Oracleconnection);

var datastore02 = new DataStore<DWtwo>(Oracleconnection);



Thread thread1 = new Thread(() => ExportDataOne(datastore01);

Thread thread2 = new Thread(() => ExportDataTwo(datastore02));



thread1.Start();

thread2.Start();

}



ExportData01(DataStore<DWone> datastore) { 100 lines of code }

ExportData02(DataStore<DWone> datastore) { 100 lines of same code as ExportData01 }



You can see how redundant this would get for 10 threads/DataStores. If I want to add more DataStores in the future it would be even more repetitive. Each ExportData##(...) does the same thing the only difference between them is the DataStore being used.