Results 1 to 3 of 3
  1. #1
    Star Lounger
    Join Date
    Jul 2002
    Posts
    54
    Thanks
    0
    Thanked 0 Times in 0 Posts

    switcing to .NET from VB (.net)

    I'm a heavy VB and VBA user...in your guys experience is it worth learning .NET at this point in time or better to wait a bit? What are your greatest frustrations with it and what are the best benefits that you are finding? Also, what are the cost implications?

  2. #2
    Star Lounger
    Join Date
    Feb 2003
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    53
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: switcing to .NET from VB (.net)

    The advantages are many and varied, but the increase in difficulty is significant. If you mainly work on office development and addins etc, I would probably wait until you have a compelling need - but start investing time now to understand how this stuff is different, and what you can do with it, so you know when to jump.
    If you are a professional programmer, I think you need to start the shift now - there is a lot to learn, and it looks to me like the volume will keep increasing.
    [Particularly note 'zero client installation' - I now have applications using Excel and Word pieces that automatically download updates when the user tries to use them: very cool!]

  3. #3
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: switcing to .NET from VB (.net)

    I agree with Steve. The great features of .net are worth learning now, but if you are going to develop for Office, wait for
    Office 11 and VSTO. There are just too many headaches and very little documentation with those darn PIAs. The object models are presented in
    what might as well be a completely separate language. If you dive now you'll find yourself learning all the nuances of glorious syntax like this
    just to return an object of commandbars:

    allBars = (CommandBars)wordApp.GetType().InvokeMember("Comma ndbars",BindingFlags.Getproperty,null,wordApp,null );
    (that's the C# flavor)

    In VBA it's simply

    set allBars = Commandbars

    You might think that wordApp.Commandbars would be a nice way to reference them, but the object invoked that way goes
    out of focus and disappears with every new document. Not very useful. And don't get me started on setting commandbar protection.

    On the bright side, I like C#, the VS IDE and all the advantages of managed code. Start the climb; the hill is steep.
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

Posting Permissions

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