Dll Property I Could Not Set

Question

0.00/5 (No votes)

See more:

Hi
i had a thrid party DLL which i registered and trying to use in my VB.net project. In my main file, i could able to create instance of the dll. But when i am trying to set property, the system got hang for a minute and come out. it is not showing any error message or it is not coming to the catch option.

Example:

foxxb.datapath = "c:\bs\vs\data" - while executing this line through debug mode, system hang up for few seconds and come out (i mean cancel)

Help any one plz

write to [REMOVED EMAIL]

Posted 19-Nov-14 20:51pm

Ramesh Iyer

Updated 19-Nov-14 21:08pm

Pikoh

v2

Add a Solution

Comments

Pikoh 20-Nov-14 3:10am

Never post your email online,the only thing you will get is spam. You should also improve your question saying what third party dll you are using. With the info you provided is impossible that someone could help you

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-11-19T22:08:00

Without knowing what the property does, and what the DLL expects, we really can't tell. And we have no idea what the DLL is, who the third party is, or any other information - so we can't be of any realistic help.

The best solution is to contact the people you got the DLL from, and ask them - or read the documentation. We have no access to either, so we can't offer any concrete solutions.