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 do you mean by table-per-type?
Explain two instances where routing is not implemented or required?
What is filters in web api?
What is difference between viewbag and viewdata and tempdata?
i have done enough testing in life but now stated developing intereset in development work,Can i think of entering into development work that too in >Net after more then 4 years of testing experiece?
Explain the types of Scaffoldings.
How to return the JSON from action method in ASP.Net MVC?
Is entity framework slow?
Explain how to use multiple submit buttons in ASP.Net MVC?
What are the possible razor view extensions?
List the new features added in .net framework 4.0.
mention what are the various methods provided by the dataset object to generate xml?
what is entityclient?
What is entity framework used for?
How would you deploy your old applications with .net framework 4.0? Are the old applications compatible?