C# tana gudanar da kuskure ta hanyar exceptions da ake kama ta try/catch/finally. Daidaita-daidaitan exception handling yana nufin kama nau'oi na exception na musamman, tsaftace alamu (sau da yawa tare da using), yin custom exceptions masu ma'ana, da rashin share kuskure a shiru.
try
{
var data = RiskyOperation();
}
catch (FileNotFoundException ex) // catch SPECIFIC types (most specific first)
{
Console.WriteLine($"File missing: {ex.Message}");
}
catch (IOException ex)
{
Log(ex);
throw; // re-throw, PRESERVING the stack trace (not `throw ex`)
}
catch (Exception ex) // catch-all (last) — base of all exceptions
{
Log(ex);
}
finally
{
Cleanup(); // ALWAYS runs (success, exception, or return)
}
Kama nau'oi na musammu exception na farko, yi amfani da Exception azaman catch-all na karshe, da finally don tsaftace-tsaftace da dole ne koyaushe ya gudana. Mahimmaci: yi amfani da throw; (ba throw ex;) don sake jefa — yana adana asalin stack trace.
if (amount < 0)
throw new ArgumentException("Amount must be positive", nameof(amount));
// a custom exception for your domain
public class InsufficientFundsException : Exception
{
public InsufficientFundsException(string message) : base(message) { }
}
throw new InsufficientFundsException("Balance too low");
// `using` guarantees Dispose() is called (close files/connections) even on exception
using (var file = new StreamReader("data.txt"))
{
var content = file.ReadToEnd();
} // file.Dispose() called automatically here
using var conn = new SqlConnection(...); // C# 8 simplified form
using statement yana tabbatar da IDisposable alamu (fayiloli, haɗi) ana tsaftace su daidai — hanya da aka zaɓa don tsaftace alamu, inda aka iya gidaje fiye da manual finally.
catch (Exception ex) when (ex.Message.Contains("timeout")) // exception filter (when)
{ ... }
✓ Catch SPECIFIC exceptions, not just Exception
✓ Use `using` for IDisposable resources (reliable cleanup)
✓ Don't swallow exceptions silently (empty catch) — log or re-throw
✓ Use `throw;` (not `throw ex;`) to preserve the stack trace
✓ Create meaningful custom exceptions; don't use exceptions for normal control flow
Daidaita-daidaitan exception handling shine mahimmaci don gina C# aikace-aikace masu ƙarfi da tabbatacce, saboda haka fahimtar shi sosai yana da mahimmanci.
try/catch/finally tsarin, kama nau'oi na musammu na exception (don tsaftace-tsaftace da ake da alaƙa) tare da Exception azaman catch-all na karshe, da finally don tsaftace-tsaftace da aka tabbatar sun kasance tushe.
Masu kyakkyawan aiki na C# da yawa suna da mahimmanci musamman: amfani da throw; maimakon throw ex; lokacin sake jefa (bayani mai subtlety amma mahimmaci — throw ex; yana sake saitin stack trace, yana rashin albashi mahimmin bayani game da debugging), amfani da using statement don IDisposable alamu (hanya da aka zaɓa, ingantaccen hanya don tabbatar fayiloli, haɗi, da sauran alamu ana tsaftace su daidai ko da lokacin da exceptions suka faru — inda aka iya gidaje fiye da manual finally blocks, da mahimmaci ne ga C# model na tsaftace alamu), da rashin share kuskure a shiru.
Fahimtar exception handling — tsarin, musammu catches, custom exceptions, stack-trace-adana re-throw, da musamman using don tsaftace alamu — yana da mahimmanci don rubuta ingantaccen C# da ke gudanar da kuskure da kyau da kula da alamu daidai.
Tun da ba'a gudda ba da exceptions da burnar alamu suna haifar da ainihin matsaloli na tsarbomewa, da tun da C# tana da musammu idioms (using tsarin, throw; adana) wanda ke tabantar ingantaccen code daga fragile code, godiya-godiya exception handling yana da mahimmanci, sannu-sannu-sannu ilhamin aiki don C# development na alalmomi.