AccessViolation Exception

  • Thread starter Thread starter Hugo Vale
  • Start date Start date
H

Hugo Vale

Hi,

I have a reference to a 3rd party dll that was designed to be used in
framework v1.1 and I'm currently trying to upgrade one of our projects to
v2.0. The problem is that the 3rd party dll does not work when referenced on
v2.0. It throws a AccessViolationException. Is there any way of forcing a
reference to use v1.1 version of the framework on a v2.0 project?

Thanks in advance
 
You'd first need to find out if this third party dll works with 2.0 from
their support site.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
 
They don't support 2.0. That 3rd party dll is part of an application that
was designed to work with 1.1. Still I was hoping that 2.0 had some kind of
mechanism that would let me force that dll to use v1.1. Is that possible?

Hugo Vale
www.datastreamcs.com


Alvin Bruney - ASP.NET MVP said:
You'd first need to find out if this third party dll works with 2.0 from
their support site.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



Hugo Vale said:
Hi,

I have a reference to a 3rd party dll that was designed to be used in
framework v1.1 and I'm currently trying to upgrade one of our projects to
v2.0. The problem is that the 3rd party dll does not work when referenced on
v2.0. It throws a AccessViolationException. Is there any way of forcing a
reference to use v1.1 version of the framework on a v2.0 project?

Thanks in advance
Click to expand...
Click to expand...
 
No. That's not possible. If your application is running under 2.0, code will
be executed under 2.0. There's no middle ground here.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



Hugo Vale said:
They don't support 2.0. That 3rd party dll is part of an application that
was designed to work with 1.1. Still I was hoping that 2.0 had some kind of
mechanism that would let me force that dll to use v1.1. Is that possible?

Hugo Vale
www.datastreamcs.com


Alvin Bruney - ASP.NET MVP said:
You'd first need to find out if this third party dll works with 2.0 from
their support site.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



Hugo Vale said:
Hi,

I have a reference to a 3rd party dll that was designed to be used in
framework v1.1 and I'm currently trying to upgrade one of our projects to
v2.0. The problem is that the 3rd party dll does not work when
Click to expand...
referenced
on
v2.0. It throws a AccessViolationException. Is there any way of forcing a
reference to use v1.1 version of the framework on a v2.0 project?

Thanks in advance
Click to expand...
Click to expand...
Click to expand...
 
Back
Top