Attempted to read or write protected memory. This is often an indication that other memory has been corrupted.

[Dick van der Sar]

I access a dll via dllimport (see below). It workes fine at framework
version 1.1 but now I try to run it in the Beta 1 of VS 2005 and I get
this error message. I have only this problem if a use this function in
a web project.
If I make a standard windows program: no problem.

[DllImport("spec ial.dll", CallingConventi on = CallingConventi on.Cdecl
)]
private static extern void specialfunction (string name, ....);

Remark:

If I use it in a web project I have to access it via a thread, strange
but it workes.
Has someone an idea?

Dick van der Sar

[Willy Denoyette [MVP]]

"Dick van der Sar" <d.******@hccne t.nl> wrote in message
news:fe******** *************** ***@posting.goo gle.com...

I access a dll via dllimport (see below). It workes fine at framework
version 1.1 but now I try to run it in the Beta 1 of VS 2005 and I get
this error message. I have only this problem if a use this function in
a web project.
If I make a standard windows program: no problem.

[DllImport("spec ial.dll", CallingConventi on = CallingConventi on.Cdecl
)]
private static extern void specialfunction (string name, ....);

Remark:

If I use it in a web project I have to access it via a thread, strange
but it workes.
Has someone an idea?

Dick van der Sar

Please post the whole DllImport function declaration and the C function
export declaration.
Make sure the calling convention is cdecl. Point is that you are passing a
wrong pointer or that are messing with the stack, what would explain why it
works from a separate thread.

Willy.

[dick van der sar]

Ok:

private void opendb()
{
ConnectServerAn dOpenDatabase(" NDBCN", "NAVISIONSERVER ", "tcp", "" ,
8000, true, false, "dick", "");
}

[DllImport("cfro nt.dll", CallingConventi on = CallingConventi on.Cdecl)]
private static extern void DBL_ConnectServ erAndOpenDataba se(string
NDBCDriverName, string ServerName, string NetType,
string DatabaseName, int CacheSize, bool UseCommitCache, bool
UseNTAuthentica tion, string UserID, string PassWord);

public void ConnectServerAn dOpenDatabase(s tring NDBCDriverName, string
ServerName, string NetType,
string DatabaseName, int CacheSize, bool UseCommitCache, bool
UseNTAuthentica tion, string UserID, string PassWord)
{
DBL_ConnectServ erAndOpenDataba se(NDBCDriverNa me, ServerName, NetType,
DatabaseName, CacheSize, UseCommitCache, UseNTAuthentica tion, UserID,
PassWord);
}
Willy: Can you also explain that you understand "what would explain why
it works from a separate thread."?

Dick
*** Sent via Developersdex http://www.developersdex.com ***

[Willy Denoyette [MVP]]

"dick van der sar" <d.******@hccne t.nl> wrote in message
news:ef******** ******@TK2MSFTN GP09.phx.gbl...

Ok:

private void opendb()
{
ConnectServerAn dOpenDatabase(" NDBCN", "NAVISIONSERVER ", "tcp", "" ,
8000, true, false, "dick", "");
}

[DllImport("cfro nt.dll", CallingConventi on = CallingConventi on.Cdecl)]
private static extern void DBL_ConnectServ erAndOpenDataba se(string
NDBCDriverName, string ServerName, string NetType,
string DatabaseName, int CacheSize, bool UseCommitCache, bool
UseNTAuthentica tion, string UserID, string PassWord);

public void ConnectServerAn dOpenDatabase(s tring NDBCDriverName, string
ServerName, string NetType,
string DatabaseName, int CacheSize, bool UseCommitCache, bool
UseNTAuthentica tion, string UserID, string PassWord)
{
DBL_ConnectServ erAndOpenDataba se(NDBCDriverNa me, ServerName, NetType,
DatabaseName, CacheSize, UseCommitCache, UseNTAuthentica tion, UserID,
PassWord);
}
Willy: Can you also explain that you understand "what would explain why
it works from a separate thread."?

Dick
*** Sent via Developersdex http://www.developersdex.com ***

Dick,

This is good but not yet enough, we need the C function declaration too,
preferably from the header file or from the documentation. Most notably we
need to know what is expected as string and bool.

When you run just this ... ConnectServerAn dOpenDatabase on a separate
thread, it might work even if you corrupt the stack, each thread has his own
stack, so when the thread proc returns it's stack is removed anyway.

Willy.