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
What is the domain object?
What are Validation Annotations?
What are the new enhancements done in default project template of asp.net mvc 4?
Which are the important namespaces used in mvc?
How do I use partial view?
Why to use '{resource}.axd/{*pathInfo}' in routing in ASP.Net MVC?
What is the meaning of unobtrusive javascript?
Which version of .net framework is installed?
Explain the role of assembly in the .net framework.
What is main objective of asp.net mvc 4 or what is new in mvc4 ?
What is storage model? : Entity framework
what is complex type?
Explain the advantages and disadvantages of ASP.Net MVC over ASP.NET?
How to Redirect Tracing to a File
What are the new features 3.5 framework against with the tool?