Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Question is pretty straight forward. Are there any valid use cases for the DebuggerStepThroughAttribute? Valid in the sense that they'd be used in a development environment.
Losing 4 solid hours, only to find this attribute decorated on a class is rather disheartening.
I have used it when developing framework code, when the source code to the framework is in the same solution as the main application.
Basically when done with the framework code, I tag the appropriate classes or methods, so that if I, as an example, step over a method call up in the application code, it will not suddenly dive into tons of framework code before resurfacing in the application code somewhere else.
Makes it easier to debug the application.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am curious when there is a correct time to use the attribute [Obsolete] and the time to just delete the code. Is this something that should be considered in certain patterns like Factory vs Builder? Thanks!
You should use it in situations where there is code that is not under your control that consumes your class and you want to make a public API change and discourage or block future usage of the old API method/property without breaking binary compatability.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I want to make an RPG and want to know if i should use Xna or Monogame to code it. What would have a better result or easier code. I've researched a bit but still cant decide.
Since Monogame is the open source version of XNA ...
In terms of API calls / code you would have to write to do something they are basically the same and were designed to be.
That's like asking ... "should I drive a blue car or a red car?" it makes no difference since both will get you from A to B.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am working in a company that wants to make a CMS program.
I say that the UI layer should be written with MVC but they say that MVP is better.
I dont know which one is good for this project or any other.
What do you think?
And they want to use WPF.
How do you think about WPF in a web project like this?
Thank you all.
Go to beside your management and say "be satisfy"
MVC is better thing.. :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Assuming I was writing my own version of .Net :)
What would be the downside of such a setup?
Yes, I am talking about a new anti-pattern here to avoid creating endless tuples and EventArgs. I think such a setup would have made coding a lot cleaner.
No. The Tag property has history, it was important in VB6 and Winforms was meant to replace it. It needed to be added to make porting code relatively simple.
It is entirely unnecessary in .NET. It supports implementation inheritance, a feature that VB6 didn't have. So if you want to add extra properties then you just derive a class and add them. And you'll be able to give them a good name and a type so you don't have to cast every time you read the property. This works just as well with Winforms controls.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I know that Web Methods are light weight and gives you speed since there is no post back. I found that a Web Method can be added to a .aspx.cs just like in .asmx.cs web service file. Is there any difference ? Any advantage or disadvantage of doing or not doing so? Or are they just two ways of doing same thing?
You often have methods that are logically dedicated to specific ASPX pages, and you don't really want them to be exposed to the public through the ASMX file. Generally, this is the most appealing reason why you want to place web methods in ASPX pages.