Re: C:\windows\assembly\GAC\ADODB for VB .net 2.0 install

Well now I'm getting somewhere. I got the program to give me a different
error message (don't ask how) but it's a .net security issue. I've got my
system administrator working on it now. I think it has something to do with
the adodb.dll calls. I did a test program that just adds it but doesn't call
anything and it worked. My program is now giving me errors when it tries to
access the sql server.


"Ellie" <nospam@xxxxxxxxxx> wrote in message
news:OCFUMmgeIHA.4140@xxxxxxxxxxxxxxxxxxxxxxx

I've got a new error. It occurs on line1:
System.InvalidOperation.exception:

The operation does not allow partially trusted callers.

I was able to create a Helloworld app and I added adodb to it (didn't call
anything though) and it ran fine. My program is doing the above. I tried
starting up a new program and adding it as the startup form but I added
something wrong. Any help as to what the above means would be appreciated.
Meanwhile I'll keep plugging away. Thanks

"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message
news:O9uVvsWeIHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
Normally a .Net executable is xcopy deployable , however when dealing
with interop to legacy components ( in your case adodb , comctl32.dll )
You need to be sure that these dependancy`s are installed and registred
correct on the target system .

To narrow the problem you might start to see if the target computer is
capable at all of running a .net prog ( just create a simple hello world
program and see if this works on the target system )

Success ?

Then create a program that uses the adodb or comctl32.dll and so on and
on

it might help to use debug executables for this ( compiled in debug modus
with pdb file and with all optimizations set to off ) cause this will
give a verry descriptive error message with most of the times an message
with the exact row number in the source where the error occured

HTH

Michel



"Ellie" <nospam@xxxxxxxxxx> schreef in bericht
news:u7ruGgUeIHA.4844@xxxxxxxxxxxxxxxxxxxxxxx
I copied my entire bin directory to the target computer, had a reference
to comctl32.ocx so I copied that and comcat.dll (and comctl32.dll for
good measure) to my target computer app directory and I'm getting that
"Has encountered an error and has to close message..." The target
computer has .net but it is in the winnt\system32 directory (not sure if
that's a problem). Do I need SqlExpress too? I didn't see that anywhere
and I don't see any sql server services running on the target computer.
My program accessed a different sql server though. Any help would be
appreciated. This is my first .net app so hopefully after I get this
going, I'll be ok for a while. Thanks


"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message
news:ut$y2zLeIHA.2000@xxxxxxxxxxxxxxxxxxxxxxx

Set all your referenced dll`s to "Copy local"=True in the properties
windows of the dll``s
now recompile your project , in your bin directory you should now see
your assembly including all dependent dll`s
if you copy all of these to a different computer with the .net
framework installed , it should work without anny problems

ofcourse asuming that all interopted COM components are already
installed on the target system


HTH

Michel

"Ellie" <nospam@xxxxxxxxxx> schreef in bericht
news:egBq9yKeIHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
I have an ADODB.dll that is in my references under the above path. Is
this something that I need to copy to the computer where I am
installing my VB .net 2.0 app? I also have a reference to
AxInterop.ComctlLib.dll which I will copy to my .exe folder and
register(?) it there. The computer already has the same version of the
2.0 framework so I guess I don't need that? I am trying to avoid a
setup program and would actually like to know exactly what is needed
for my program to run on a different computer without the development
environment. Thanks











.

Relevant Pages
Quantcast