Changes to which portion of version number indicates an incompatible change
Answer / 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 |
what is dot net? what is use dot net? what is benifit of dot net?what is vb dot net? what is ado dot net? what is c#?
Explain encapsulation
1 Answers HPCL, Hughes Systique Corporation,
Explain ASP.NET MVC Identity and Security?
What does mvvm mean?
Is dapper better than entity framework?
Possible ways to prevent xss attacks on mvc application?
Explain JSON Binding?
Is it possibe to run 2 aplication on single m/c, one App is on .Net Framework 1.0 and another one is on .Net Fremework 2.0?
Explain covariance and contra-variance in .net framework 4.0. Give an example for each.
mention what is the difference between ado.net and classic ado?
What is oauth in web api?
what is client wins and store wins mode in entity framework concurrency?