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
explain how you can load related entities in ef (entity framework)?
Is entity framework slow?
Why to use '{resource}.axd/{*pathInfo}' in routing in ASP.Net MVC?
Explain Sections is ASP.Net MVC?
In .net compact framework, can we free memory explicitly without waiting for garbage collector to free the memory?
Explain the 'page lifecycle' of an ASP.NET MVC?
How to update one of my table in database at 4pm every day how it is possible?
What is viewstart page in mvc?
Asp.net mvc application, makes use of settings at 2 places for routing to work correctly. What are these 2 places?
If I have multiple filters implemented, what is the order in which these filters get executed?
In razor syntax, what is the escape sequence character for @ symbol?
what is entity framework?
Does Tempdata hold the data for other request in ASP.Net MVC?
how can you enhance the performance of entity framework?
Explain the advantages and disadvantages of ASP.Net MVC over ASP.NET?