|
Codes in FACILITY_ITF
These HRESULTSs with facilities such as FACILITY_NULL and FACILITY_RPC have universal meaning
because they are defined at a single source: Microsoft. However, HRESULTs in FACILITY_ITF are determined by the interface method (or function) from
which they are returned. That is, the same 32-bit value in FACILITY_ITF returned
from two different interface methods might have different meanings.
The reason HRESULTs in FACILITY_ITF can have different meanings in different interfaces is that HRESULTs are kept to an efficient data type size of 32 bits. Unfortunately 32 bits is
not large enough for the development of an allocation system for error codes
that avoid conflict between codes allocated by different non-communicating
programmers at different times in different places (unlike the handling of interface
IDs and CLSIDs). As a result, the 32-bit HRESULT is structured in a way that Microsoft can define some universally-defined
error codes, while allowing other programmers to define new error codes without
fear of conflict. The status code convention is as follows:
- Status codes in facilities other than FACILITY_ITF can only be defined by Microsoft.
- Status codes in facility FACILITY_ITF are defined solely by the developer of
the interface or API that returns the status code. To avoid conflicting error
codes, whoever defines the interface is responsible for coordinating and
publishing the FACILITY_ITF status codes associated with that interface.
All the OLE-defined FACILITY_ITF codes have a code value in the range of
0x0000 0x01FF. While it is legal to use any codes in FACILITY_ITF, it is recommended
that only code values in the range of 0x0200 0xFFFF be used. This recommendation is made as a means of reducing confusion
with any OLE-defined errors.
It is also recommended that developers define new functions and interfaces to
return error codes as defined by OLE and in facilities other than FACILITY_ITF.
In particular, interfaces that have any chance of being remoted using RPC in
the future should define the FACILITY_RPC codes as legal. E_UNEXPECTED is a
specific error code that most developers will want to make universally legal.
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|