Changes to which portion of version number indicates an incompatible change
Answer Posted / kirti
Major or minor. Changes to the major or minor portion of the version number indicate an incompatible change. Under this convention then, version 2.0.0.0 would be considered incompatible with version 1.0.0.0. Examples of an incompatible change would be a change to the types of some method parameters or the removal of a type or method altogether. Build. The Build number is typically used to distinguish between daily builds or smaller compatible releases. Revision. Changes to the revision number are typically reserved for an incremental build needed to fix a particular bug. You'll sometimes hear this referred to as the "emergency bug fix" number in that the revision is what is often changed when a fix to a specific bug is shipped to a customer.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
How to change the action name in ASP.Net MVC?
Explain the .net framework.
What are HTML Helpers, AJAX Helpers in ASP.Net MVC?
What is a razor file?
Is http stateful or stateless?
What are the 2 ways of adding constraints to a route?
Explain the request flow in asp.net mvc framework?
Explain the methods used to render the views in ASP.Net MVC?
What are the major improvements provided by the common language runtime and the base class libraries? Or what are the major improvements in .net framework 4.0?
Is it possible to unit test an mvc application without running the controllers in an asp.net process?
What is MVVM design pattern?
What happens when I install the .net framework 3.0? How can I upgrade if I already have the .net framework 2.0 installed?
Give an example for authorization filters in an asp.net mvc application?
Does razor engine supports for tdd?
what is entity framework advantage?