CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2009
    Posts
    73

    Question Consequence of using API methods which are for "Microsoft Internal Use Only."

    Hi,

    In some of the API methods in C#, there is a section in the help which states the following:

    "This API supports the .NET Framework infrastructure and is not intended to be used directly from your code.
    Microsoft Internal Use Only. "

    Are you aware of any bad consequences which might occur to a developer using these API methods anyway?

    Beside the fact that Microsift might not be responsible to support this API methods, and might even remove them from the API in future versions, are there any other kind of bad consequences which might occur (e.g., the code might not work properly in certain environemnts/terms, or there might be legal problems in using these methods)?

    Thanks

  2. #2
    Join Date
    Jun 2004
    Location
    Kashmir, India
    Posts
    6,808

    Re: Consequence of using API methods which are for "Microsoft Internal Use Only."

    I am not aware of any legal norms around these APIs, however as you already wrote they might be removed in the future.

    If you can tell us which API you are talking about, we might be able to provide some specific input.

  3. #3
    Join Date
    Jan 2002
    Location
    Scaro, UK
    Posts
    5,940

    Re: Consequence of using API methods which are for "Microsoft Internal Use Only."

    From my experience, using undocumented and unsupported APIs opens a whole world of pain when it comes to installation of your software.

    Some clients will be able to install and run your software, some won't - giving you a very bad rep.

    I'd avoid them if I were you. There are usually alternatives.

    Darwen.
    www.pinvoker.com - PInvoker - the .NET PInvoke Interface Exporter for C++ Dlls.

  4. #4
    Join Date
    Apr 2009
    Posts
    73

    Thumbs up Re: Consequence of using API methods which are for "Microsoft Internal Use Only."

    Thanks,

    That's what I was afraid of... I'll try to avoid using them...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  





Click Here to Expand Forum to Full Width

Featured