Deploy application without installing MS office on server side

[John]

I have a vb.net application developed using VS 2003. The components that the
application referenced are Microsoft.office.core verison 11, Interop.word and
interop.excel. This application is a dll and will be deployed into window
2003 server of my company production environment for other applications, such
as Biztalk to call to create documents run-time.

Since my company don't allow to install offcie application on production
server, this dll can not run there. Would someone give me some recommendation
that how I can resolve the problem?

Thanks in advance

John

 

[Jonathan West]

I have a vb.net application developed using VS 2003. The components that
the
application referenced are Microsoft.office.core verison 11, Interop.word
and
interop.excel. This application is a dll and will be deployed into window
2003 server of my company production environment for other applications,
such
as Biztalk to call to create documents run-time.

Since my company don't allow to install offcie application on production
server, this dll can not run there. Would someone give me some
recommendation
that how I can resolve the problem?

Don't use those components....

Seriously, if you know components are not going to be available on the
target machine, you have to design not to use them.if your app *must* use
those components in order to work, then you must ensure that they are
available.

If the components are necessary but it is known they are going to be
unavailable, then you don't agree to do the job in the first place!


--
Regards
Jonathan West - Word MVP
www.intelligentdocuments.co.uk
Please reply to the newsgroup
Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org

 

[Steve Rindsberg]

I have a vb.net application developed using VS 2003. The components that the
application referenced are Microsoft.office.core verison 11, Interop.word and
interop.excel. This application is a dll and will be deployed into window
2003 server of my company production environment for other applications, such
as Biztalk to call to create documents run-time.

Since my company don't allow to install offcie application on production
server, this dll can not run there. Would someone give me some recommendation
that how I can resolve the problem?

As Jonathan points out, you can't automate an application that isn't installed.

You could possibly install it on a standalone PC that has access to a shared
folder on the server; the application could "watch" the folder for incoming
files, process them and then save them to a "done" folder, also on the server.