Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

Is installing Office 2003 a must for using Visual Tools for Microsoft Office System (with VS.NET 2003)?

 

Could it be used with Office XP (2002), or perhaps just the new libraries would be enough (version 11)?

 

Please help, because I'm in a quite a big trouble!

Thanks!

  • 4 weeks later...
Posted

Is installing Office 2003 a must for using Visual Tools for Microsoft Office System (with VS.NET 2003)?

 

Yes, MS has moved its developing platform for MS Office to .NET which require the latest version

 

Kind regards,

Dennis

Posted

Well... I've worked with Office XP and Office 2003 on both VS.NET 2002 and VS.NET 2003.

 

What it used to do is only to import the right Interop DLL. So as long as your version of office have a COM that is compatible with VS.NET ... It'll probably work.

"If someone say : "Die mortal !"... don't stay to see if he isn't." - Unknown

"Learning to program is like going out with a new girl friend. There's always something that wasn't mentioned in the documentation..." - Me

"A drunk girl is like an animal... it scream at everything like a cat and roll in the grass like a dog." - Me after seeing my girlfriend drunk and some of her drunk friend.

C# TO VB TRANSLATOR

Posted

Hummmm... Am I having hallucination ?

 

Well... I'm with Office XP at my work... and I'm working with Office in my ASP.NET and WinForms application.

 

Here is information from the reference :

Name : Interop.Microsoft.Office.Core

Description : Microsoft Office 10.0 Object Library (OfficeXP, 2003 is 11.0)

 

Well... maybe I'm crazy but you might explain why you said this :

 

Yes' date=' MS has moved its developing platform for MS Office to .NET which require the latest version[/quote']Because I'm working with Office XP (2002) dll and it's not the latest version (refereing to 2003) and everything is working.

 

Explain me because your misleading me. :-\

 

(Unless you are refer to the office object under .NET tab)

"If someone say : "Die mortal !"... don't stay to see if he isn't." - Unknown

"Learning to program is like going out with a new girl friend. There's always something that wasn't mentioned in the documentation..." - Me

"A drunk girl is like an animal... it scream at everything like a cat and roll in the grass like a dog." - Me after seeing my girlfriend drunk and some of her drunk friend.

C# TO VB TRANSLATOR

Posted

Thanks for the precision.

 

Yeah it seems cool. Since it don't act as COM object (while still being one) anymore and can reduce production time.

 

I'll have to keep up to date and keep an eye on the developement of this. My first preoccupation about this... is the version of office. Will further version will have backward compatibility ? I mean by this... it's using Office 2003. Not everybody have it. What about further version of VSTO ? And what about Office 2004 VSTO and Office 2005 VSTO ? Will they support Office 2003 VSTO or will user will be forced to update their Office version ?

 

Hummmm... so much questions... so few anwser..... AAAGRRRRRRRRRRR !!!!

:p lollll

"If someone say : "Die mortal !"... don't stay to see if he isn't." - Unknown

"Learning to program is like going out with a new girl friend. There's always something that wasn't mentioned in the documentation..." - Me

"A drunk girl is like an animal... it scream at everything like a cat and roll in the grass like a dog." - Me after seeing my girlfriend drunk and some of her drunk friend.

C# TO VB TRANSLATOR

Posted

I agree that is a little bit confusing and it raise more questions then there are answers to...

 

Anyway, using the COM-approach to automate office will still be a valid and workable way with .NET and I guess this will be the de facto standard as long as we still need to work with older versions, i e 97 and above, of Office.

 

In pure technical terms it's about controling unmanaged code with managed code ;)

 

MS has always had a good strategy for backward compatibility but since .NET represent a total different technical-platform then we need to accept the changes.

 

But as long as the COM-approach is available we are assured to have a backward compatibility.

 

As for VSTO, it's still under developing like VS.NET itself so let see what the next coming versions next year will contain :)

 

Kind regards,

Dennis

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...