This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
It is possible to have an option to add the attribute "DebuggerStepThrough" for each properties of the LightSpeed model. When I debug with visual studio and a step into, I'm not interested to enter in the model of LightSpeed.
Thank you. |
|
|
|
|
We thought this was such a good idea we're not even making it an option -- we think it should just happen. It will be in tonight's build -- let us know if you encounter any problems. (NOTE: The implementation required a change to the code gen template files. If you are using a custom template, be sure to merge the changes into your custom template files.) |
|
|
|
|
Forgot to mention: we actually went with emitting DebuggerNonUserCodeAttribute rather than DebuggerStepThroughAttribute, because it's more convenient on properties. As far as I can tell, this isn't going to have any unintended side effects, but the docs are a bit confusing. Again, let us know if we need to revisit this. |
|
|
|
