Hello,

I am getting the following error when using the VisualCron API dlls in an ASP.NET application.

Could not load file or assembly 'VisualCron, Version=1.0.1.33564, Culture=neutral, PublicKeyToken=55f7a52402de1c04' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Are the dlls build with an old version of .NET?

What am I doing wrong?

I am using the .NET Framework 2.0.

Thanks.

Did you try using the dll:s from the program files/VisualCron/ folder? (not from sub folder). Try creating a new project and add the files from the VisualCron folder.

---

Hello,

I just tried and it doesn't work.

I am also getting the following error in a 64bit environment.(It works fine in a non 64bit environment.)

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Source Error:

Line 277: #endregion
Line 278:
Line 279: Client c = new Client();
Line 280: Connection conn = new Connection();
Line 281: conn.Address = address;

I think there was another thread discussing this on the forum but no solution was provided.

So, to summarize this:

1. you have no problems with VS 2008 using 32bit OS?
2. you get reference error in VS 2008 when using 64bit OS?
3. You get an exception in ASP.NET when using dll in 64bit OS?

---

Yes. That is so strange.

In fact the app works on my 64bit machine when I use it in debug mode.

As soon as I deploy it on a 64bit machine, it throws the memory error.

I got the reference error when trying to create a new fresh web application. It worked the first time.

I tried this on two 64bit computers running IIS 7 and it failed. I tried it on a 32 bit computer running IIS 6 and it worked fine.

Thank you.

We will prepare an environment for testing this and will get back to you. Thank you for your patience.

---

Just to verify again:

1. do you get any errors in development environment (VS2008)? Or only when deploying?
2. The development environment is 64 bit as well?

---

Just to verify again:

1. do you get any errors in development environment (VS2008)? Or only when deploying?
2. The development environment is 64 bit as well?

1. I didn't get the memory error when developing the application with VS2008. Only when deploying it in IIS 7.
2. The development environment is 64 bit as well.

Thank you.

Hello,

Do you have any updates on this issue?

Thank you.

Sorry for the delay. Please test with the attached files.

---

Thank you.

I will try this ASAP.

Sorry for the delay. Please test with the attached files.

It is working for me.

Thank you very much.