Changes to which portion of version number indicates an incompatible change
- 1 Answers
- 2007 Views
- I also Faced
- E-Mail Answers
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 |
Why is the .net framework 3.0 a major version number of the .net framework if it uses the .net framework 2.0 runtime and compiler?
what is the additional features in 1.1 rather than 1.0
Is .net framework dead?
I couldnot answer for projects bcz i have 2+ fake experience.can you please tell me how to answer..?
Can any particular component of .net framework 3.0 be removed?
mention what is the difference between ado.net and classic ado?
mention what is csdl, ssdl and msl sections in an edmx file?
What is Reference type and value type
Hello frnds, Actually i am plannig to put fake Xperince letter is it good or not, and please suggest me from where we take it.
What is the use of dataadapter ?
What are the possible razor view extensions?
What are the versions of .net framework?
Dot Net Framework 
