Re: New Platform Invoke Resource for Developers

From: Michel Gallant (neutron_at_NOSPAMistar.ca)
Date: 03/10/04


Date: Wed, 10 Mar 2004 14:01:35 -0500

Thanks Jesse,
Very good idea.
Just to bring folks here up to date, I have published a rather large number of articles
on P/Invoke to CryptoAPI at:
    www.jensign.com
While much of the pinvoked functionality described in the samples will be available
via .NET Framework V2, there are some techniques and complexities associated
with pinvoking to CryptoAPI that will be of interest.

Most samples are in C# (appologies to VB.NET but life is short, and I come from a Java background
:-)
and most have a fair amount of technical description.

Please feel free to link to this site. I noticed you already linked to one of my
MS .NET/Crypto articles.

Best,
- Mitch Gallant
   MVP Security
   www.jensign.com

"Jesse Kaplan" <jessek@online.microsoft.com> wrote in message news:404f5cbb$1@news.microsoft.com...
> Platform Invoke Resources
>
>
>
> In our efforts to make the .Net platform continuously easier to develop for
> we have reviewed developer feedback and help requests from Product Support
> Services, Microsoft.dotnet newsgroups, and other
> blogs(http://blogs.msdn.com/brada/archive/2004/02/06/69095.aspx) and message
> boards we've taken on the task to relieving or minimizing the major pain
> point of using Platform Invoke from VB.Net and C#. After floating around
> proposals through blogs and PSS we analyzed the feedback and found a wide
> range of suggestions. They ranged from "write a tool that would list every
> possible signature and usage for each method and every possible declaration
> for every structure" to "we should make P\Invoke even harder to use to
> encourage developers to stay away from it."
>
> After analyzing all this data we believe that what will help developers the
> most is a way to find all the resources that are currently available, and
> that most problems could be solved with currently available help, if it
> could only be found. To that end we compiled a list resources that should
> provide assistance to any developer, beginner or advanced, encountering
> problems with VB.Net\C# P\Invoke functionality:
>
> http://www.gotdotnet.com/team/clr/bcl/TechArticles/TechArticles/PInvokeHelp/FAQ.aspx
>
>
>
> This is only a temporary home for this resource. We are posting this to get
> more feedback from developers (you) who have had in the past or are
> currently having problems with P\Invoke. We want to know if this compilation
> of resources would have helped you or has helped you solve your problem, and
> if not, what additional resources do you think would further enhance the
> developer experience. We'll take your feedback into consideration before we
> post this resource on MSDN.
>
>
>
> Thank you,
>
> The CLR Team
>
>
>
>



Relevant Pages

  • New Platform Invoke Resources for Developers
    ... Platform Invoke Resources ... we have reviewed developer feedback and help requests from Product Support ... Services, Microsoft.dotnet newsgroups, and other blogs and message boards we ...
    (microsoft.public.dotnet.framework.clr)
  • New Platform Invoke Resource for Developers
    ... Platform Invoke Resources ... we have reviewed developer feedback and help requests from Product Support ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: New Platform Invoke Resource for Developers
    ... with pinvoking to CryptoAPI that will be of interest. ... > Platform Invoke Resources ... > we have reviewed developer feedback and help requests from Product Support ...
    (microsoft.public.dotnet.languages.csharp)
  • New Platform Invoke Resource for Developers
    ... Platform Invoke Resources ... we have reviewed developer feedback and help requests from Product Support ...
    (microsoft.public.dotnet.languages.vb)
  • Re: New Platform Invoke Resource for Developers
    ... with pinvoking to CryptoAPI that will be of interest. ... > Platform Invoke Resources ... > we have reviewed developer feedback and help requests from Product Support ...
    (microsoft.public.dotnet.languages.vb)