This question is locked. New answers and comments are not allowed.
Given this line of code:
Three EQATEC files are created at that location named storage_(stuff).bin. The next time I run the app, all three files are used again.
Given this line of code that I want to use to support a Citrix environment:
I end up with three files initially, just like above, and they start with my domain/username to make them distinct from other users. When I start the app a second time, a second session file is created. When I start the app a third time, a third session file is created, giving me 5 files total.
This does not seem to be intended behavior. This directory will end up with a number of files approaching the number of times the app has been started. I'm assuming this is a bug? Do you have a workaround?
See screenshot for what my EQATEC directory ends up looking like. The timestamps are off for the two files that don't get duplicated, but that only happened once. Usually those two do get an updated timestamp.
analyticsSettings.StorageInterface = AnalyticsMonitorFactory.CreateStorage(EqatecLogsFileShare);
Three EQATEC files are created at that location named storage_(stuff).bin. The next time I run the app, all three files are used again.
Given this line of code that I want to use to support a Citrix environment:
analyticsSettings.StorageInterface = AnalyticsMonitorFactory.CreateStorage(EqatecLogsFileShare, Environment.UserDomainName + Environment.UserName);
I end up with three files initially, just like above, and they start with my domain/username to make them distinct from other users. When I start the app a second time, a second session file is created. When I start the app a third time, a third session file is created, giving me 5 files total.
This does not seem to be intended behavior. This directory will end up with a number of files approaching the number of times the app has been started. I'm assuming this is a bug? Do you have a workaround?
See screenshot for what my EQATEC directory ends up looking like. The timestamps are off for the two files that don't get duplicated, but that only happened once. Usually those two do get an updated timestamp.