Results 1 to 4 of 4

Thread: VBA2DotNet or DotNet

  1. #1
    Member
    Join Date
    2008-07
    Location
    Brisbane (Australia)
    Posts
    19
    Login to Give a bone
    0

    Cool VBA2DotNet or DotNet

    With the demise of VBA in AutoCAD, I am left pondering .. which is best.

    Migrate VBA code to DotNet as noted in the various videos that can be found at the Autodesk webiste or on the net

    OR

    Start over and rewrite the code in DotNet for smother integration.
    (The latter would mean more of a learning curve for me)

    Your valuable input would be most appreciated.

  2. #2
    Active Member
    Join Date
    2006-08
    Location
    Brisbane : GMT+10
    Posts
    87
    Login to Give a bone
    0

    Default Re: VBA2DotNet or DotNet

    Hello Eddie,
    Long time no see

    The .NET learning curve IS considerable.
    Become familiar with the framework and IDE.
    Become proficient with .NET development in AutoCAD.
    Become familiar with the managed wrappers for the ARX functions in AutoCAD.

    You may be best served just translating from VBA to .NET retaining the COM/ActiveX usage you are familiar with.
    There is some reasonable guidance available in articles at
    The AutoDESK Developers Site.
    The AutoDESK University Lectures
    'ThroughTheInterface' Blog.

    We'll leave the C#/VB discussion for a more suitable venue

    good fortune !
    be well.

  3. #3
    Member
    Join Date
    2008-07
    Location
    Brisbane (Australia)
    Posts
    19
    Login to Give a bone
    0

    Default Re: VBA2DotNet or DotNet

    Kerry,

    Mate how are you, it sure has been a long time.

    Yes my plan is to move across to DotNet.
    The question was aimed at understanding if it would be better to rewrite in .net or migrate the VBA to .net as per the examples shown in AutoCAD_VBA_to_NET_Migration video that can be found on the net.

    At this stage i'm thinking migration whilst a rewrite is in progress.



    Quote Originally Posted by Kerry Brown View Post
    Hello Eddie,
    Long time no see

    The .NET learning curve IS considerable.
    Become familiar with the framework and IDE.
    Become proficient with .NET development in AutoCAD.
    Become familiar with the managed wrappers for the ARX functions in AutoCAD.

    You may be best served just translating from VBA to .NET retaining the COM/ActiveX usage you are familiar with.
    There is some reasonable guidance available in articles at
    The AutoDESK Developers Site.
    The AutoDESK University Lectures
    'ThroughTheInterface' Blog.

    We'll leave the C#/VB discussion for a more suitable venue

    good fortune !
    be well.

  4. #4
    AUGI Addict
    Join Date
    2015-12
    Posts
    2,095
    Login to Give a bone
    0

    Default Re: VBA2DotNet or DotNet

    Best bet, I think, would be migration first *then* rewriting. It will get your feet wet while getting things going in the least amount of time. As you get better you can redo the various modules as learning projects.

Similar Threads

  1. DotNet Visual Lisp
    By dmarcotte4 in forum API Wish List
    Replies: 26
    Last Post: 2012-09-08, 06:32 PM
  2. Installing ACAD 2011 dotNet Wizards
    By sec.bvba520978 in forum ARX
    Replies: 1
    Last Post: 2011-06-22, 08:34 PM
  3. AutoCAD dotnet object model? + C# Plotting
    By schrodingerscat in forum Dot Net API
    Replies: 8
    Last Post: 2009-01-06, 09:52 PM
  4. Combine dwfs with DotNet?
    By mweaver in forum Dot Net API
    Replies: 2
    Last Post: 2007-10-29, 10:53 AM

Posting Permissions

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