MSDOTnet.org Forum Index
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

That assembly does not allow partially trusted callers

 
Post new topic   Reply to topic    MSDOTnet.org Forum Index -> ODBC Dotnet
Author Message
Stephen



Joined: 08 Aug 2007
Posts: 5

PostPosted: Tue Jul 03, 2007 9:54 am    Post subject: That assembly does not allow partially trusted callers Reply with quote

VS2005 app cannot access a call to an ODBC conection. I get a security
warning"
That assembly does not allow partially trusted callers."

I have a strong name for the project set in the project.

What do I have to do to allow this application to be called from a file
server instead of the local drive.

Is there a way to set the data tier's dll to the local drive? If so how do
I set up the base project to not look for that dll in the bin directory?

TIA

__Stephen

Archived from group: microsoft>public>dotnet>framework>odbcnet
Back to top
View user's profile Send private message
Display posts from previous:   
Related Topics:
How do i include Microsoft.Data.Odbc.dll assembly ?? hi want to use mysql with Visual Studio NET (C++) and i want to try get a connection with MySQL I think I need to include the assembly. Can anyone suggest me, how can I add that ? currently iam getting the following error, iam sure it

MDAC 2.8 Primary Interop Assembly (PIA) / PIA download site Does someone know where can I get the primary interop assembly (PIA) for ActiveX Data Objects (ADO) in MDAC 2.8 version? The following article: talks about a

Unable to emit assembly: Referenced assembly does not have a "Unable to emit assembly: Referenced assembly does not have a strong name" I have a COM+ application built using vb.net, it has several components, all of which are native components inherited from

About Assembly How can I add some extern assembly reference to an assembly I generate in program ? I use program to generate a assembly, when i see its MANIFEST with ildasm, it has only ..assembly extern mscorlib { = (B7 7A 5C 56 19 34 E0 89 )

Big assembly vs small one Hello How big assembly with numerous namespaces can affect performance of the application. I understand that the overhead is on start when the assembly is loaded, but isn't better then constant overhead with small assemblies? TIA Vadym
Post new topic   Reply to topic    MSDOTnet.org Forum Index -> ODBC Dotnet All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group