|
Home > Archive > MS SQL Server MSEQ > June 2005 > Deploying vb.net english query application
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Deploying vb.net english query application
|
|
| Tinium 2005-04-15, 7:23 am |
| Hi,
I'm attempting to distribute a vb.net english query application to a
client, however, when the client runs the application, it crahses when
it tries to create an instance of the "Mseq.Session" object.
As far as I can tell, the interop and the original dll are being
included in the setup correctly - are there any special settings (such
as com registration, system etc), or other files that I should be
including? Or are there any other prerequisits for the client's pc
before I can expect the software to run?
Cheers,
Tinium.
| |
| Guy Cox 2005-06-09, 3:23 am |
| you are still going to need to install the EQ engine on the target
platform.. There's an awful lot of work done by the engine before the query
is shipped off the Server. EQ is a client function..
Guy
"Tinium" <tin@ium.com> wrote in message
news:eWfltpaQFHA.132@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I'm attempting to distribute a vb.net english query application to a
> client, however, when the client runs the application, it crahses when it
> tries to create an instance of the "Mseq.Session" object.
>
> As far as I can tell, the interop and the original dll are being included
> in the setup correctly - are there any special settings (such as com
> registration, system etc), or other files that I should be including? Or
> are there any other prerequisits for the client's pc before I can expect
> the software to run?
>
> Cheers,
> Tinium.
|
|
|
|
|