Page 1 of 2 12 LastLast
Results 1 to 15 of 22
  1. #1
    Star Lounger
    Join Date
    Jan 2001
    Location
    Switzerland
    Posts
    90
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Next Office VB (11)

    Folks,

    I have been following the recent threads here with curiosity but I am still confused about what choices, if any, we will have with Office 11. Anyone testing the next release of Office ? Without breaking too much of the NDA what should we expect in terms of the "new" programming language ? Is there any public documentation (even limited) available ?


    --alex

  2. #2
    Super Moderator
    Join Date
    Dec 2000
    Location
    New York, NY
    Posts
    2,970
    Thanks
    3
    Thanked 29 Times in 27 Posts

    Re: Next Office VB (11)

    Alex,

    I'm still waiting to get my hands on the Office 11 beta (channels move very slowly at my firm), but since no one else has answered: I did briefly see it installed on someone else's laptop and it appeared that the VB Editor was not enabled for any of the Office apps - I don't know if that reflects that individual user not having fully registered their copy, or whether the beta does not have the VB Editor enabled at all.

    If I learn more about this in the next week or so I'll post back, but my betting for now is that Office 11 will still be plain ol' VBA, with VS.Net/VB.Net programability for Office not arriving until version 12. (and if anyone out there knows differently, I'd be glad to hear a hint....)

    Gary

  3. #3
    Star Lounger
    Join Date
    Jan 2001
    Location
    Switzerland
    Posts
    90
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Next Office VB (11)

    Gary,

    Actually things seem to be moving on that very topic: http://news.com.com/2100-1001-976488...t=dht&tag=ntop

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

    Re: Next Office VB (11)

    I see nothing in that article that implies that Office 11 will include VSA.
    The VS .NET Roadmap stated that Office will be .NET-ized in the time frame of the Yukon release of VS .NET.

    MSFT is close to releasing the Eureka release of VS .NET.

    So, unless they intend to quickly follow that with the Yukon release, I don't see how Office 11 would be .NET-ized, i.e., include VSA.

  5. #5
    Star Lounger
    Join Date
    Jan 2001
    Location
    Switzerland
    Posts
    90
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Next Office VB (11)

    Well, I did not want to imply otherwise...

    My understanding is that Office 11 will be VBA only. VBA will get some built-in support for .net (access to web services) and VS 2003 will have some support to hook into Office 11 (details not quite clear on that front).

    --alex

  6. #6
    Star Lounger
    Join Date
    Jan 2001
    Location
    Switzerland
    Posts
    90
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Next Office VB (11)


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

    Re: Next Office VB (11)

    Alex,
    This is what we have been waiting to hear from MS! I'm an Office 11 Beta 1 and this
    is definitely *NOT* included. All you get is VBA 6.03 -- same as XP but with the new
    objects.

    So, MS is lighting a fire under the .Net/Office folks to
    get this VSO (let's call it?) into Office for the -- hopefully -- the next beta release.

    I can't see how they can go live (in June/July?) without another beta round, especially
    if this Visual Studio for Office is going to be in the RTM.

    I'd say right here and now to my fellow Lounge coders: get .Net and get up to speed.
    My little but ever increasing exposure to .net so far reveals that .net is all it's cracked
    up to be. It's an awesome IDE and OOP coding is -- though often strange and new -- wild.

    Thanks for the link. Hate to admit it, but even though I cruise all the Office 11 pages, I'd not seen this yet!

    p.s. Gary, does this look exciting or what?
    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>

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

    Re: Next Office VB (11)

    Kevin, you'd better hope they don't rush the .Net implementation just to please all those who are hot to program in it! We all know how that sort of thing turns out because we've seen service releases on new versions of Office that come out before the shrinkwrap has cooled on the initial release!
    Charlotte

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

    Re: Next Office VB (11)

    I know I sound a bit excited, but have you tried VS .Net yet? Sure, there are a few shortcomings already,
    but nothing that outweights the good.

    See if you can get it installed and take a look. You'll love it.
    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>

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

    Re: Next Office VB (11)

    Kevin,

    There's a lot of good stuff. I wish I'd had some of that when I was coding ASP last year.

    One thing I really don't like though- I can't change code on the fly. In VB/VBA, I can set a breakpoint, run the code to the breakpoint, and play around with the code For jobs like tweaking colours or positions finely, that's really useful. But in .NET, I have to stop and rerun to see changed code. For something where I might have to go through 10 steps to see the change, it's a pain.
    Subway Belconnen- home of the Signboard to make you smile. Get (almost) daily updates- follow SubwayBelconnen on Twitter.

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

    Re: Next Office VB (11)

    This is true, but certain coding attempts would not take without a "recompile".
    Changing an object reference comes to mind. So, you could not *always* change
    code in debug mode. But you still have the immediate window to play with. Look at the
    stack window, the breakpoint window -- what a joy! -- the locals, etc.

    Gee wiz, I expect to see a kitchen sink window.

    Maybe we'll just grow to be better progammers, I don't know.
    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>

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

    Re: Next Office VB (11)

    Not better, Kevin, just different. Every new OS or language or any major change to an existing one looks like the greatest thing ever ... for a while. I remember when DOS replaced CP/M and LANs became possible. <img src=/S/granny.gif border=0 alt=granny width=20 height=20> <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  13. #13
    Super Moderator
    Join Date
    Dec 2000
    Location
    New York, NY
    Posts
    2,970
    Thanks
    3
    Thanked 29 Times in 27 Posts

    Re: Next Office VB (11)

    Kevin,

    That part about VS Tools for Office is an eye-opener. In addition to that, I had previously been unaware that you could already program Office XP, after a fashion, using VS.Net and something called the Office XP Primary Interop Assemblies (as discussed in the previous article in the series).

    The difference between that and VS Tools for Office (if I can be excused for posting a small quote from Paul Cornell's first article):
    <hr>Note that this is different than the Office XP Primary Interop Assemblies (PIAs). The Office XP PIAs allow Visual Studio .NET project code to externally automate Office XP; however, Office XP does not associate your customization with a specific Office document, template, or workbook. In contrast, "Visual Studio Tools for Office" allow "Office 11" developers to write managed code extensions in Visual Studio .NET 2003 that execute behind "Word 11" documents or templates and "Excel 11" workbooks. You get the full advantage of the Visual Studio .NET 2003 and .NET Framework environments, thereby allowing you to create .NET based solutions and migrate your existing "Word 11" and "Excel 11" solutions over to .NET, over time and as it makes sense to your business.
    <hr>
    This is just an interim solution until full .Net programmability for Office arrives with Office 12, but it does open up the possibility of starting a migration to .Net with Office 11, rather than waiting for Office 12. Considering that VB app development is moving toward .Net, and that - as Woody notes in this week's W.O.W. - VBA is destined for orphanhood, this adds a lot more weight to the case for moving toward .Net sooner rather than later.

    Now here's a possible twist: other than additions for new features, there have been no major changes to the VBA object models for most of the Office apps, since VBA arrived - and this will not change with Office 11 either, based on the code samples in the article. Is there any chance that MS might decide to make major changes (improvements/fixes) in the structure of the Office apps object models, for Office 12? If that happened, then everything previously written in VBA or .Net would have to be rewritten - so I guess I don't think that will happen (and when does MS ever go back and fix old stuff?); which means we will be using powerful new .Net-enabled languages, to program the same old creaky, flaky Office object models! <img src=/S/laugh.gif border=0 alt=laugh width=15 height=15>

    Gary

  14. #14
    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: Next Office VB (11)

    I need help understanding "code behind" in relation to something other than a web page. I understand that in going from ASP to ASP.NET, Microsoft encourages putting the "script" in a separate file, called the code behind file, rather than mixing it in with the presentation code as we did in the old ASP days. But in the context of an Office document, what is a code behind file?? Is it something other than a template, global template, or COM Add-in? Does it actually attach to a file like a second attached template? Is it embedded?

  15. #15
    Super Moderator
    Join Date
    Dec 2000
    Location
    New York, NY
    Posts
    2,970
    Thanks
    3
    Thanked 29 Times in 27 Posts

    Re: Next Office VB (11)

    In terms of Word or Excel, I've always interpreted 'code behind the file' as simply meaning the VBA code that is part of that file's VBA project - though technically it may be in a .bas or .frm file that is associated with the .doc or .xls, rather than part of the document file itself - from the visualization that you are in the document, then Alt+F11 over to the VBE and there is the document's code - 'behind' the file.

    Never having worked with these, I guess the Office XP PIA's allow you to create something like a COM Add-in - which can operate upon objects, including documents, in an application, but the code is not associated with a specific document or template. Whereas in contrast, what the Visual Studio Tools should let you do is something very similar to what you do with Office VBA, which is to associate code directly with a particular document, template etc. So rather than doing your Office app VBA programming within the old VBE environment, it appears you could move the development work entirely into the VS.Net environment - no small news.

    Or are you getting at something else entirely, which I am missing? <img src=/S/grin.gif border=0 alt=grin width=15 height=15>

Page 1 of 2 12 LastLast

Posting Permissions

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