|
|
Rank: Newbie
Groups: Member
Joined: 12/14/2018
Posts: 4
|
Quote:
[KeyNotFoundException: Verilen anahtar sözlükte yoktu.]
System.Collections.Generic.Dictionary`2.get_Item(TKey key) +12775381
EO.Internal.d0.a(String A_0) +93
EO.Internal.am1.a(String A_0) +67
EO.Internal.ahr..ctor(String A_0) +172
EO.Internal.ly.j() +984
EO.Internal.aid..ctor() +34
EO.Internal.w.b(Type A_0) +1021
EO.Internal.am1.a(Type A_0) +59
EO.Internal.am1..cctor() +341
[TypeInitializationException: 'EO.Internal.am1' tür başlatıcısı özel durum döndürdü.]
EO.Internal.am1.h() +17
EO.Web.Control..ctor(Type implType) +95
EO.Web.ASPXToPDF..ctor() +77
ASP.aspxtopdf_aspx.__BuildControlASPXToPDF1() in c:\Program Files (x86)\Essential Objects\EO.Total 2018\Samples\CS\Pdf\PdfWeb_CS\ASPXToPDF.aspx:13
ASP.aspxtopdf_aspx.__BuildControlform1() in c:\Program Files (x86)\Essential Objects\EO.Total 2018\Samples\CS\Pdf\PdfWeb_CS\ASPXToPDF.aspx:11
ASP.aspxtopdf_aspx.__BuildControlTree(aspxtopdf_aspx __ctrl) in c:\Program Files (x86)\Essential Objects\EO.Total 2018\Samples\CS\Pdf\PdfWeb_CS\ASPXToPDF.aspx:1
ASP.aspxtopdf_aspx.FrameworkInitialize() in c:\Program Files (x86)\Essential Objects\EO.Total 2018\Samples\CS\Pdf\PdfWeb_CS\ASPXToPDF.aspx.cs:912307
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +48
System.Web.UI.Page.ProcessRequest() +72
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +22
System.Web.UI.Page.ProcessRequest(HttpContext context) +58
ASP.aspxtopdf_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\vs\dd693703\c97b50b6\App_Web_paf0uiko.8.cs:0
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +188
System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +48
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +71
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
Hi,
We can not think of any reason that can cause this problem rather than our DLLs have been modified/tampered. Do you see the same problem on a different machine?
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/14/2018
Posts: 4
|
Yes I see the same problem on other machine. Icreated new project on other machine then I get same error.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
I am not sure what we can tell you because we have not seen this problem anywhere else. So the only way for us to find out the root cause is to test it in your environment. Is it possible for you to prepare a test machine and provide us RDP access to the machine so that we can investigate further?
|
|
Rank: Newbie
Groups: Member
Joined: 9/16/2015
Posts: 6
|
I've never had TypeInitializationException with specifically the EO components, but in general when I've had a TypeInitializationException and I've had too many of them to remember, it boiled down to either (a) the projects in the solution not being on the same platform (e.g. x86), (b) the projects in the solution not being on the same .NET framework version, or (c) a component (DLL) referenced in the solution was wired to load a "legacy" version of a component, like MSFT Unity or whatever, used in a newer incarnation elsewhere in the solution and thus causing everything to fail.
|
|
Rank: Newbie
Groups: Member
Joined: 12/14/2018
Posts: 4
|
I received that error on original demo solution also. I downloaded it from eo website and installed it. I didnt touch anything only opened Visual Studio 2013
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
Hi,
We can not think of anything that can cause this. We will need remote access to your computer in order to investigate this issue further. Please let us know if this is possible.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/10/2012
Posts: 1
|
I have the same problem. The components seem to not work using Visual Studio 2019 and EO 2019. I get The type initializer for 'EO.Internal.am1' threw an exception. I might have to ask for a refund and remove EO completely from my projects.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
Greg Hannah wrote:I have the same problem. The components seem to not work using Visual Studio 2019 and EO 2019. I get The type initializer for 'EO.Internal.am1' threw an exception. I might have to ask for a refund and remove EO completely from my projects. The most common scenario for you to receive this error is when you: 1. Installed a newer version on your system; 2. Then open an existing project that uses an older version of our DLLs; This would cause conflict between the two versions (one in your application's bin folder that contains the runtime DLLs and one in your "Program Files" folder that contains the design time support DLLs). To resolve this issue you would need to update your project reference to use the new DLLs, rebuild your project and then restart Visual Studio. If this is not the case or this does not resolve the issue please let us know.
|
|