469,592 Members | 2,030 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,592 developers. It's quick & easy.

Catch reference error how?

Hi there,

I've got a Windows project with references to an ocx file.
When I run the executable and the referenced ocx isn't
available I get a Windows error.

How can I trip a reference error so that I can display a
readable error message?
Tx a lot,

Dikbill, The Netherlands
di********@hotmail.com
Aug 22 '06 #1
2 1145
"Dikbill" <di********@hotmail.comschrieb:
I've got a Windows project with references to an ocx file.
When I run the executable and the referenced ocx isn't
available I get a Windows error.

How can I trip a reference error so that I can display a
readable error message?
I suggest to deploy the application using a setup (MSI package) which will
make sure the OCX file gets installed properly on the destination machine.
By choosing this approach you won't have to work around about deployment
problems in your own source code.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Aug 22 '06 #2
Thanx for your quick response.
I do already use a MSI package but users sometimes
remove the ocx/dlls which are needed.
Then they get a message which realy says nothing of what is
wrong at that time.

I want to give a clear error message so they can call out support
number with a good error message so the time to resolve the problem
will be as short as possible.

Thnx again,

Dikbill, The Netherlands
di********@hotmail.com
"Herfried K. Wagner [MVP]" <hi***************@gmx.atschreef in bericht
news:eK**************@TK2MSFTNGP02.phx.gbl...
"Dikbill" <di********@hotmail.comschrieb:
>I've got a Windows project with references to an ocx file.
When I run the executable and the referenced ocx isn't
available I get a Windows error.

How can I trip a reference error so that I can display a
readable error message?

I suggest to deploy the application using a setup (MSI package) which will
make sure the OCX file gets installed properly on the destination machine.
By choosing this approach you won't have to work around about deployment
problems in your own source code.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Aug 22 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Anand Pillai | last post: by
4 posts views Thread by Chris Martin | last post: by
2 posts views Thread by Greg Merideth | last post: by
reply views Thread by JohnR | last post: by
5 posts views Thread by JohnR | last post: by
17 posts views Thread by cashdeskmac | last post: by
7 posts views Thread by dick | last post: by
reply views Thread by suresh191 | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.