GIS Converter - EnsureDebugArgs in Console App

Question

GIS Converter - EnsureDebugArgs in Console App

Dani_S 5,261

Hi Michel,

Thank you very much for your help !!!

I implemented all your remarks from ticket:

https://learn.microsoft.com/en-us/answers/questions/5658212/gis-cli-commands

1.Do I used EnsureDebugArgs in a best way ? if not give please me the fixes code ?

EnsureDebugArgs.txt in Program.cs for debugging purposes.

2.It possible to make a loop instead on testing one by one ?

3.Files

Program code:

GitConverter ConsoleApp README.txt

Program.txt

Thanks in advance,

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

2 answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Harry Vo (WICLOUD CORPORATION) 3,910 Microsoft External Staff Moderator

Hi @Dani_S , thanks for reaching us here on our platform!

1.Do I used EnsureDebugArgs in a best way ? if not give please me the fixes code ?

No, not really. The idea is correct, but the implementation has issues:

EnsureDebugArgs is never reached because Main returns early.
It mixes too many responsibilities (arg validation, scenario building, test harness) which is not really a good decision.
It relies on hard-coded, repetitive blocks that are hard to maintain.
The args.Length >= 6 check is brittle and will break if the CLI evolves.

2.It possible to make a loop instead on testing one by one ?

Yes, a loop-based approach is clearly better and should fully replace the old code. It'll help you reduce duplication, easier to add/remove scenarios, has only one place to change paths and much easier to review and maintain.

Harry Vo (WICLOUD CORPORATION) 3,910 Reputation points Microsoft External Staff Moderator

2025-12-17T10:37:25.0433333+00:00
Main will no longer return early:

private static void Main(string[] args) { Console.OutputEncoding = System.Text.Encoding.UTF8; args = EnsureDebugArgs(args); Environment.Exit(Run(args)); }

Harry Vo (WICLOUD CORPORATION) 3,910 Microsoft External Staff Moderator

Here is an example Loop-based scenario builder:

private static Dictionary<string, string[]> BuildDebugScenarios(string baseDir) 
{     
	var scenarios = new Dictionary<string, string[]>(StringComparer.OrdinalIgnoreCase);     
	void AddGroup(string group, int count, string format)     
	{         
		for (int i = 1; i <= count; i++)         
		{             
			var key = $"{group}{i}";             
			scenarios[key] = new[]             
			{                 
				"gis_convert",
				Path.Combine(baseDir, group, "Input", $"{key}.7z"), 
				format,
				Path.Combine(baseDir, group, "Output", key), 
				Path.Combine(baseDir, group, "Temp", key),
				"Log",
				Path.Combine(baseDir, group, "Log", $"{key}_log.txt")
			};         
		}     
	}     
	AddGroup("Shapefile", 4, "Shapefile");     
	AddGroup("Csv", 3, "Csv");     
	AddGroup("Gml", 5, "Gml");     
	return scenarios; 
}

Dani_S 5,261 Reputation points

2025-12-17T11:26:41.1633333+00:00

Sorry I added the wrong file:

Please use this:

Program.txt

Does you answer change ?
Dani_S 5,261 Reputation points

2025-12-17T12:05:05.2566667+00:00

Cn you please supply modified code?
Harry Vo (WICLOUD CORPORATION) 3,910 Reputation points Microsoft External Staff Moderator

2025-12-18T09:53:52.8266667+00:00
Hi @Dani_S , thanks for sharing the updated version!

Does you answer change ?

Yes, part of my previous answer still applies, with a small adjustment.

EnsureDebugArgs still mixes multiple responsibilities. Please separated them for easier management.

You still use the large repetitive switch block. You can check my loop snippet above.

The args.Length >= 6 check is still brittle
if (args != null && args.Length >= 6) return args;
This assumes the CLI shape will never change. If additional optional arguments are introduced later, this condition may stop working as intended.

Dani_S 5,261

Hi Harry,

Thanks you very much for your answer.

I attached the last file:Program.txt

I looked on your code, and is not solved the problem.

Please for debugging only I need to:

1.Run all samples .

Option to run only one scenario for debugging.

3.This your code, the extension of your format is only 7z it can be any extension.

private static Dictionary<string, string[]> BuildDebugScenarios(string baseDir)

{

**var scenarios = new Dictionary<string, string[]>(StringComparer.OrdinalIgnoreCase);**     

**void AddGroup(string group, int count, string format)**     

**{**         

	**for (int i = 1; i <= count; i++)**         

	**{**             

		**var key = $"{group}{i}";**             

		**scenarios[key] = new[]**             

		**{**                 

			**"gis_convert",**

			**Path.Combine(baseDir, group, "Input", $"{key}.7z"),** 

			**format,**

			**Path.Combine(baseDir, group, "Output", key),** 

			**Path.Combine(baseDir, group, "Temp", key),**

			**"Log",**

			**Path.Combine(baseDir, group, "Log", $"{key}_log.txt")**

		**};**         

	**}**     

**}**     

**AddGroup("Shapefile", 4, "Shapefile");**     

**AddGroup("Csv", 3, "Csv");**     

**AddGroup("Gml", 5, "Gml");**     

**return scenarios;**

}

Please for Release I need not the debug code

Thanks in advance,

Harry Vo (WICLOUD CORPORATION) 3,910 Microsoft External Staff Moderator

Hi @Dani_S , sorry I misunderstood at 7z file, here is my implement code:

private static string[] EnsureDebugArgs(string[] args)
{
#if DEBUG
    if (args != null && args.Length >= MIN_REQUIRED_ARGS)
        return args;
    var baseDir = Environment.GetEnvironmentVariable("GISCONVERTER_TEST_BASE")
                    ?? @"D:\GisConverter\Tests";
    var scenarios = BuildDebugScenarios(baseDir);
    var debugTarget = Environment.GetEnvironmentVariable("GISCONVERTER_DEBUG_TARGET")?.Trim().ToLowerInvariant();
    // Special case: run all scenarios in sequence
    if (debugTarget == "all")
    {
        Console.WriteLine("Running all debug scenarios:");
        Console.WriteLine();
        foreach (var kvp in scenarios.OrderBy(s => s.Key))
        {
            Console.WriteLine($"Executing scenario: {kvp.Key}");
            Console.WriteLine(new string('-', 60));
            var exitCode = Run(kvp.Value);
            Console.WriteLine($"Result: {(ExitCode)exitCode}");
            Console.WriteLine();
        }
        Environment.Exit(0);
    }
    // Try to return the requested single scenario
    if (!string.IsNullOrWhiteSpace(debugTarget) && scenarios.TryGetValue(debugTarget, out var selectedArgs))
    {
        Console.WriteLine($"Debug mode: using scenario '{debugTarget}'");
        Console.WriteLine();
        return selectedArgs;
    }
    // If no valid scenario was specified, show available options
    if (!string.IsNullOrWhiteSpace(debugTarget))
    {
        Console.WriteLine($"Warning: Unknown scenario: '{debugTarget}'");
    }
    Console.WriteLine("Available scenarios (set GISCONVERTER_DEBUG_TARGET):");
    foreach (var key in scenarios.Keys.OrderBy(k => k))
    {
        Console.WriteLine($"  - {key}");
    }
    Console.WriteLine("  - all (runs all scenarios)");
    Console.WriteLine();
    return Array.Empty<string>();
#else
    return args ?? Array.Empty<string>();
#endif
}
/// <summary>
/// Builds a dictionary of all debug scenarios with correct file extensions.
/// </summary>
private static Dictionary<string, string[]> BuildDebugScenarios(string baseDir)
{
    var scenarios = new Dictionary<string, string[]>(StringComparer.OrdinalIgnoreCase);
    void AddScenario(string scenarioKey, string format, string inputFileName)
    {
        var formatFolder = format;
        scenarios[scenarioKey] = new[]
        {
            "gis_convert",
            Path.Combine(baseDir, formatFolder, "Input", inputFileName),
            format,
            Path.Combine(baseDir, formatFolder, "Output", scenarioKey),
            Path.Combine(baseDir, formatFolder, "Temp", scenarioKey),
            "Log",
            Path.Combine(baseDir, formatFolder, "Log", $"{scenarioKey.ToLowerInvariant()}_log.txt")
        };
    }
    // Shapefile test cases
    AddScenario("shapefile1", "Shapefile", "ShapeFiles.7z");
    AddScenario("shapefile2", "Shapefile", "Vector.7z");
    AddScenario("shapefile3", "Shapefile", "לא סטטוטורי - גבול מחוז מאוחד.7z");
    AddScenario("shapefile4", "Shapefile", "שכבות מידע (Arc View).7z");
    // Csv test cases - note the different extensions
    AddScenario("csv1", "Csv", "features.7z");
    AddScenario("csv2", "Csv", "features.csv");
    AddScenario("csv3", "Csv", "features.zip");
    // Gml test cases
    AddScenario("gml1", "Gml", "gml_with_attribute_collection_schema.7z");
    AddScenario("gml2", "Gml", "gml_with_attribute_collection_schema.zip");
    AddScenario("gml3", "Gml", "gml_without_attribute_collection_schema.7z");
    AddScenario("gml4", "Gml", "gml_without_attribute_collection_schema.gml");
    AddScenario("gml5", "Gml", "gml_without_attribute_collection_schema.zip");
    return scenarios;
}

Dani_S 5,261 Reputation points

2025-12-19T11:45:57.83+00:00

Thank you very much.

1.You can see the results for all tests using :'all'

or single 'csv1'

https://app.screencast.com/HOc1zu5kTQLDj

2.There is still one warnings in my Program.cs, acn you please help.

Warning:

Severity Code Description Project File Line Suppression State Details

Warning (active) CS8625 Cannot convert null literal to non-nullable reference type. GisConverter.ConsoleApp D:\GIT\GitConverterEngine\GisConverter\GitConverter.ConsoleApp\Program.cs 305

Code:

Program.txt

Maybe it connected to other files we didn't handle yet (convert method).

Answer 2

To ensure that you are using EnsureDebugArgs effectively in your console application, it is essential to focus on the following aspects:

Argument Validation: Make sure that EnsureDebugArgs checks for the required arguments before proceeding with the main logic of your application. This can prevent runtime errors due to missing or incorrect parameters.
Error Handling: Implement appropriate error handling within EnsureDebugArgs to provide informative feedback to the user if the arguments are not as expected. This can include throwing exceptions or logging errors.
Code Clarity: Ensure that the code within EnsureDebugArgs is clear and well-commented, so that other developers (or future you) can easily understand its purpose and functionality.

Regarding your second question about implementing a loop instead of testing one by one, you can certainly iterate through a collection of inputs or parameters. This can be done using a foreach loop or a for loop, depending on your specific needs. Here’s a simple example:

foreach (var arg in args) {
    // Process each argument
    EnsureDebugArgs(arg);
}

This way, you can handle multiple arguments in a more efficient manner.

If you provide the specific implementation of EnsureDebugArgs, I could offer more tailored suggestions.

References:

Dani_S 5,261 Reputation points

2025-12-17T10:06:48.18+00:00

Hi Michel ,

Is it the best way?

Thanks in advance,

Share via

GIS Converter - EnsureDebugArgs in Console App

2 answers

Your answer