000			02334nam a22003975i 4500
001			vtls000540477
003			RU-ToGU
005			20210922081700.0
007			cr nn 008mamaa
008			160915s2014 xxu| s |||| 0|eng d
020			_a9781430266716 _9978-1-4302-6671-6
024	7		_a10.1007/978-1-4302-6671-6 _2doi
035			_ato000540477
040			_aSpringer _cSpringer _dRU-ToGU
050		4	_aQA75.5-76.95
072		7	_aUY _2bicssc
072		7	_aCOM014000 _2bisacsh
082	0	4	_a004 _223
100	1		_aRahman, Mohammad. _eauthor. _9444693
245	1	0	_aC# Deconstructed _helectronic resource _cby Mohammad Rahman.
260			_aBerkeley, CA : _bApress : _bImprint: Apress, _c2014.
300			_aX, 172 p. 43 illus. _bonline resource.
336			_atext _btxt _2rdacontent
337			_acomputer _bc _2rdamedia
338			_aonline resource _bcr _2rdacarrier
520			_aC# Deconstructed answers a seemingly simply question: Just what is going on, exactly, when you run C# code on the .NET Framework? To answer this question we will dig ever deeper into the structure of the C# language and the onion-skin abstraction layers of the .NET Framework that underpins it. We’ll follow the execution thread downwards, first to MSIL (Microsoft Intermediate Language) then down through just-in-time compilation into Machine Code before finally seeing the results executed at the hardware level. The aim of this deep-dive is to provide you with a much more rounded knowledge of the environment within which you code exists. As a managed language, it’s best-practice to let the Framework deal with device interaction but you’ll find the experience of taking the cover off once in a while a very rewarding one that will greatly enrich your appreciate of the C# language and the way in which in functions.
650		0	_aComputer Science. _9155490
650	1	4	_aComputer Science. _9155490
650	2	4	_aComputer Science, general. _9155491
710	2		_aSpringerLink (Online service) _9143950
773	0		_tSpringer eBooks
856	4	0	_uhttp://dx.doi.org/10.1007/978-1-4302-6671-6
912			_aZDB-2-CWD
999			_c397844