Hi,
it's well known that debugging with #D works partial slowly. I found out that the attributes mentioned above are ignored. It would be helpful if the following statements would work in #D debugger:
string configPath = String.Empty;
public string ConfigPath {
[System.Diagnostics.DebuggerStepThrough]
get { return configPath; }
}
Especially in typed datasets, the debugger always steps into the DataSet.Designer.cs and shows each single step like:
[System.Diagnostics.DebuggerNonUserCodeAttribute()]
public string Name {
get { return ((string)(this[this.tableUserRight.NameColumn])); }
set { this[this.tableUserRight.NameColumn] = value; }
}
It's difficult always to switch between F10 and F11. It's impossible to avoid the steps above if I want to debug the following LogfileStart method step by step:
UserRightRow row = ...
LogfileStart(row.Name, row.Data, mainSettings.ConfigPath);
In this case the debugger steps 2 times into the DataSet.Designer.cs und 1 time into the MainSettings class before I can debug the LogfileStart method.
Juergen
Version 2.1.0.2429
I did'nt found these keywords by searching in the forum; therefore I suppose that this request is not yet posted.