.NET Gotchas

Name: .NET Gotchas | 75 Ways to Improve Your C# and VB.NET Programs
Brand: O'Reilly
Price: 33.99 EUR
Availability: OnlineOnly

75 Ways to Improve Your C# and VB.NET Programs

Venkat Subramaniam(Author)

O'Reilly (Publisher)

Published on 24. May 2005

396 pages

E-Book

PDF with Adobe-DRM

System requirements

978-1-4493-6271-3 (ISBN)

€33.99incl. 7% vat

System requirements

for PDF with Adobe-DRM

E-Book Single Licence

Available for download

Description

More details

Other editions

Content

Cover
Table of Contents
Preface
Who This Book Is For
How This Book Is Organized
What You Need to Use This Book
Measure of Performance
Conventions Used in This Book
Using Code Examples
Comments and Questions
Safari® Enabled
Acknowledgments
CLR/Framework Gotchas
# 1 Type alias size doesn't match what you're familiar with
In a nutshell
# 2 struct and class differ in behavior
In a nutshell
# 3 Returning value types from a method/property is risky
In a nutshell
# 4 You can't force calls to your value-type constructors
In a nutshell
# 5 String concatenation is expensive
In a nutshell
# 6 Exceptions may go unhandled
In a nutshell
# 7 Uninitialized event handlers aren't treated gracefully
In a nutshell
# 8 Division operation isn't consistent between types
In a nutshell
# 9 Typeless ArrayList isn't type-safe
In a nutshell
# 10 Type.GetType( ) may not locate all types
In a nutshell
# 11 Public key reported by sn.exe is inconsistent
In a nutshell
Visual Studio and Compiler Gotchas
# 12 Compiler warnings may not be benign
In a nutshell
# 13 Ordering of catch processing isn't consist across languages
In a nutshell
# 14 Type.GetType( ) might fail at run-time
In a nutshell
# 15 rethrow isn't consistent
In a nutshell
# 16 Default of Option Strict (off) isn't good
In a nutshell
# 17 Versioning may lead to Serialization headaches
In a nutshell
# 18 Creating Web apps can be painful
In a nutshell
# 19 Naming XML documentation for IntelliSense support isn't intuitive
In a nutshell
Language and API Gotchas
# 20 Singleton isn't guaranteed process-wide
In a nutshell
# 21 Default performance of Data.ReadXML is poor
In a nutshell
# 22 enum lacks type-safety
In a nutshell
# 23 Copy Constructor hampers exensibility
In a nutshell
# 24 Clone( ) has limitations
In a nutshell
# 25 Access to static/Shared members isn't enforced consistently
In a nutshell
# 26 Details of exception may be hidden
In a nutshell
# 27 Object initialization sequence isn't consistent
In a nutshell
# 28 Polymorphism kicks in prematurely
In a nutshell
# 29 Unit testing private methods is tricky
In a nutshell
Language Interoperability Gotchas
# 30 Common Language Specification Compliance isn't the default
In a nutshell
# 31 Optional parameters break interoperability
In a nutshell
# 32 Mixing case between class members breaks interoperability
In a nutshell
# 33 Name collision with keywords breaks interoperability
In a nutshell
# 34 Defining an array isn't consistent
In a nutshell
Garbage Collection Gotchas
# 35 Writing Finalize( ) is rarely a good idea
In a nutshell
# 36 Releasing managed resources in Finalize( ) can wreak havoc
In a nutshell
# 37 Rules to invoke base.Finalize( ) aren't consistent
In a nutshell
# 38 Depending on Finalize( ) can tie up critical resources
In a nutshell
# 39 Using Finalize( ) on disposed objects is costly
In a nutshell
# 40 Implementing IDisposable isn't enough
In a nutshell
# 41 Using the Dispose Design Pattern doesn't guarantee cleanup
In a nutshell
Inheritance and Polymorphism Gotchas
# 42 Runtime Type Identification can hurt extensibility
In a nutshell
# 43 Using new/shadows causes "hideous hiding"
In a nutshell
# 44 Compilers are lenient toward forgotten override/overrides
In a nutshell
# 45 Compilers lean toward hiding virtual methods
In a nutshell
# 46 Exception handling can break polymorphism
In a nutshell
# 47 Signature mismatches can lead to method hiding
In a nutshell
Multithreading Gotchas
# 48 The Thread class supports some dangerous methods/properties
In a nutshell
# 49 Foreground threads may prevent a program from terminating
In a nutshell
# 50 Background threads don't terminate gracefully
In a nutshell
# 51 Interrupt ( ) kicks in only when a thread is blocked
In a nutshell
# 52 ThreadAbortException-a hot potato
In a nutshell
# 53 Environment.Exit( ) brings down the CLR
In a nutshell
# 54 ResetAbort( ) may lead to surprises
In a nutshell
# 55 Abort( ) takes time to clean up
In a nutshell
# 56 Calling Type.GetType( ) may not return what you expect
In a nutshell
# 57 Locking on globally visible objects is too sweeping
In a nutshell
# 58 Threads from the thread pool are scarce
In a nutshell
# 59 Threads invoked using delegates behave like background threads
In a nutshell
# 60 Passing parameters to threads is tricky
In a nutshell
# 61 Exceptions thrown from threads in the pool are lost
In a nutshell
# 62 Accessing WinForm controls from arbitrary threads is dangerous
In a nutshell
# 63 Web-service proxy may fail when used for multiple asynchronous calls
In a nutshell
# 64 Raising events lacks thread-safety
In a nutshell
COM-Interop and Enterprise Services Gotchas
# 65 Release of COM object is confusing
In a nutshell
# 66 Using interface pointers after calling ReleaseComObject( ) will fail
In a nutshell
# 67 Cross-apartment calls are expensive
In a nutshell
# 68 Default apartment of main thread is inconsistent across languages
In a nutshell
# 69 STAThread attribute may have no effect on your methods
In a nutshell
# 70 Spattering access to COM components makes code hard to maintain
In a nutshell
# 71 Auto-generating GUID for your classes leads to versioning woes
In a nutshell
# 72 All but one of the ClassInterface options are ineffective
In a nutshell
# 73 Simply tur ning the switch for COM interop is dangerous
In a nutshell
# 74 ServicedComponents implemented inconsistently on XP and 2003
In a nutshell
# 75 AutoComplete comes with undesirable side effects
In a nutshell
Resources
Bibliography
On the Web
Index

System requirements

Save as PDF Copy link into clipboard

Schweitzer Fachinformationen

.NET Gotchas

Description

More details

Other editions

Additional editions

Content

System requirements