[AccessD] No Office 2003 ODE (Office Developer Edition)?

RE: [AccessD] No Office 2003 ODE (Office Developer Edition)?a.. One of the most frequently asked questions is will Office 2003 support .NET. Yes and no is the answer. Use Visual Studio Tools for Office to automate documents and workbooks using Visual Basic .NET (or Visual C# .NET) that's written in the in the next version of Visual Studio-Visual Studio .NET 2003. This is good news for the Office developers that are using .NET elsewhere as they won't have to wait for .NET to actually be incorporated in Office in the proper sense. While it isn't a full Office .NET package, it's more than XP offers, which supports limited .NET customization that can't associate .NET routines with a specific Office file. Those of you already in the process of moving to .NET can get a jump on Word and Excel applications. 
I don't think that really answers anyone's questions, but... 

Susan H. 
  ----- Original Message ----- 
  From: Jack Dolby 
  To: 'Access Developers discussion and problem solving' 
  Sent: Thursday, August 07, 2003 2:38 PM
  Subject: RE: [AccessD] No Office 2003 ODE (Office Developer Edition)?


  What is being developed is not a vba-equivalent program in dotnet... it is an automation application. 

  Thus you are creating a dotnet app (usually in vb.net since there are some c# issues with the 2003 tools under c#) that will create or act upon word or excel files.

  As far as I know, MS has not even started rumors on when dotnet would migrate into the world currently occupied by vba. 

  The dotnet office tools are, as stated earlier, only for word and excel 2003. 

  Hth, 

  jack 
  --- 
  I've wrestled with reality for 35 years, doctor, 
  and I'm happy to state I finally won out over it. 
  Elwood P. Dowd 
    
    
  -----Original Message----- 
  From: Charlotte Foust [mailto:cfoust at infostatsystems.com] 
  Sent: Thursday, August 07, 2003 2:34 PM 
  To: Access Developers discussion and problem solving 
  Subject: RE: [AccessD] No Office 2003 ODE (Office Developer Edition)? 

  I think the idea is that you develop it in VS.Net and then deploy it in 
  *either* Word or Excel. 

  Charlotte Foust 

  -----Original Message----- 
  From: Gustav Brock [mailto:gustav at cactus.dk] 
  Sent: Thursday, August 07, 2003 9:53 AM 
  To: Access Developers discussion and problem solving 
  Subject: Re: [AccessD] No Office 2003 ODE (Office Developer Edition)? 



  Hi Jim 

  > Ken Getz did a demo of the Excel/Word tools last week at VSLive. These 

  > are really neat tools that let you develop a Word or Excel application 

  > from within Visual Studio. 

  But why should one do that? 

  I'm still confused on a higher level. No wonder MS asks in surveys to 
  their dealers if we understand .net strategy and if we promote it to our 
  clients. 
  And boy if the asked the same about Access and Access development? What 
  answer could I possibly give? 

  /gustav 

  _______________________________________________ 
  AccessD mailing list 
  AccessD at databaseadvisors.com 
  http://databaseadvisors.com/mailman/listinfo/accessd 
  Website: http://www.databaseadvisors.com 
  _______________________________________________ 
  AccessD mailing list 
  AccessD at databaseadvisors.com 
  http://databaseadvisors.com/mailman/listinfo/accessd 
  Website: http://www.databaseadvisors.com 



------------------------------------------------------------------------------


  _______________________________________________
  AccessD mailing list
  AccessD at databaseadvisors.com
  http://databaseadvisors.com/mailman/listinfo/accessd
  Website: http://www.databaseadvisors.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030807/7d3561e6/attachment-0001.html>