Results 1 to 8 of 8
  1. #1
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Office and .NET (VB .NET and C#)

    Most of the folkes, who do programming, in these forums seem to be most interested in programming for Office.

    VB .NET is, so far, clearly easier to use than C# for Office programming, even in VSTO.

    VB .NET is not going to go away, unless MSFT comes up with a way to "easily" migrate VBA code to C#.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Office and .NET (VB .NET and C#)

    Did you have a question, Howard, or are you simply stating an opinion? If you use ASP.Net, you are forced to use C# syntax in some places, even if you're programming in VB.Net.
    Charlotte

  3. #3
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office and .NET (VB .NET and C#)

    I was referring only to Office programming.

  4. #4
    Platinum Lounger
    Join Date
    Dec 2000
    Location
    Queanbeyan, New South Wales, Australia
    Posts
    3,730
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office and .NET (VB .NET and C#)

    Howard

    Whatever your preference, there is a commercial reality. And the reality is that there is a demand for C# as well as VB.Net.

    My shop changed from VB.Net to C# for a lot of reasons. No single reason was compelling- but the entirety was big enough to convert all previously VB.Net to C#.

    A well funded government agency can afford to do that- indeed it can afford to redevlop from the ground up.

    Some of the reasons they changed.
    .VB is viewed as a small developers' language to some extent. C++ used to be the MS language of choice- now it's C#
    .Some support for VB language features is apparently due to be phased out
    .It was felt that developers would not bring aboard old, bad habits if they started with a new language
    .Conversion from VB6 was not an option.
    .There were some things which could be done in C# which could not be done in VB.Net.

    I had no say in the process, and I am not saying that one language is better than the other. But they are converging- and the difference seems to be getting closer to bottom level syntax rather than the fundamental differences in language philosophy which we used to see. The process of converting from VB.Net to C# was a quite straight forward process.

    I'm not most folkes, but I no longer do Office programming. Just large applications.
    Subway Belconnen- home of the Signboard to make you smile. Get (almost) daily updates- follow SubwayBelconnen on Twitter.

  5. #5
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office and .NET (VB .NET and C#)

    Your statements do not contradict what I stated.

  6. #6
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Office and .NET (VB .NET and C#)

    Geoff, was there any particular training regimen to get the VB/VB.Net people up to speed on C# as quickly and efficiently as possible? Since it's the government, I assume you didn't just furlough them and hire newbies. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  7. #7
    Platinum Lounger
    Join Date
    Dec 2000
    Location
    Queanbeyan, New South Wales, Australia
    Posts
    3,730
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office and .NET (VB .NET and C#)

    Jefferson

    A good question- but not a short answer.

    The big learning curves were .Net, object oriented, and a completely new architecture.

    They hired .Net wizzes to build the architecture, and then trained up the people who new the systems well to build the applications on top,

    Our team members (about 15 developers, and contractors) were given the option of doing a training course. These normally cost $A1800 to $A2500 (about $US 1200 to $1800) for a one week course- we were given a $500 subsidy, but the course was after hours. That was in VB.Net.

    The switch from VB.Net to C# was much smaller that the initial VB.Net.

    I've since been on another one week course- the client paid, but it was during work hours, so I missed out on a week's pay. I'd been doing C# for some months at that stage, the course complemented a lot of concepts.

    The rewrite (not a conversion) will take a lot of years- but they are taking advantage of the opportunity to respec, and build a much better new system.

    In the meantime, VB6 applications are being maintained, and interact with the .Net components.
    Subway Belconnen- home of the Signboard to make you smile. Get (almost) daily updates- follow SubwayBelconnen on Twitter.

  8. #8
    Platinum Lounger
    Join Date
    Dec 2000
    Location
    Queanbeyan, New South Wales, Australia
    Posts
    3,730
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office and .NET (VB .NET and C#)

    My apologies Howard. I was merely relating experiences from my site, which may have been of use to some.

    I did not realise it was a requirement to contradict you.
    Subway Belconnen- home of the Signboard to make you smile. Get (almost) daily updates- follow SubwayBelconnen on Twitter.

Posting Permissions

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