Managed code usage survey


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I just completed a survey on managed
code usage internally.  It was very
informal, but I think we got some good general directions. = o ns = "urn:schemas-microsoft-com:office:office" />


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I thought I’d validate some of that
by asking you folks some of the more interesting questions… Please respond in my
comments or send me an email: BradA at Microsoft dot com.


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Please pass the link
along!


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 


style="mso-bidi-font-weight: normal"> style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">When do you plan to release your
first solution based on managed code?


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">(Please chose
one)


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-tab-count: 1">           
Already have


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-tab-count: 1">           
Within 3 months


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-tab-count: 1">           
Within 6 months


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-tab-count: 1">           
Within 1 year


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-tab-count: 1">           
Within 2 years


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-tab-count: 1">           
Further out


style="mso-bidi-font-weight: normal"> style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 


style="mso-bidi-font-weight: normal"> style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Why is your team using Managed code?


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">(Chose as many as you’d
like)


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Expose APIs to 3rd party
developers


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Ease of development


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Security/Reliability


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Plug into other managed technology
(ASP. "urn:schemas-microsoft-com:office:smarttags" /> style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">NET style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">, VS, etc)


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Other (please
specify)


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> style="mso-spacerun: yes"> 


style="mso-bidi-font-weight: normal"> style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">What are the biggest impediments to
using managed code in your team or in more parts of your
application?


style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 

Comments (5)

  1. Dima says:

    1. Already have
    and
    2. Ease of development
    Security/Reliability

  2. Mehul Mahimtura says:

    1. Already Have
    2a. Expose APIs to 3rd party developers.
    2b. Other – Use the exposed API to write a telephony server application.
    3. Have not come across any big impediments.

  3. Steve Hiner says:

    1. Already have
    2. Ease of development / .NET Rocks
    3. Execution speed. Actually the entire app is in managed code but I wish it ran faster. In future projects the impediments are primarily customer acceptance and the fact that some of our customers don’t have good enough hardware to run .NET apps adequately. I dread going back to VB6 or Access on future projects but it’s probably unavoidable.

  4. Adam Hill says:

    1. Already have
    2.. Ease of development , plug into ASP.NET and Web Services.
    3. a) A managed IE control.
    b) Layerable, alpha channelable windows form controls.
    c) A SmartCard wrapper in C# from MS.
    d) HW Accelerated Managed GDI+

    Hopefully MS will get serious about those of us who have to write media rich apps in .NET and can’t use DX because we dont want to rewrite all WinForm controls from scratch 🙂

  5. 1. Already Have one
    2.Ease of development
    Plug into other managed technology (ASP.NET, VS, etc)
    3. None.. Fully Managed Code.