DAAB问题 [英] DAAB problem

查看:102
本文介绍了DAAB问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

现在我来自VB6背景,所以我可能会在这里忽略一些东西。


我的功能包含在2个VB 2005 dll中。


WARC_Subs_Reporting.dll处理报告函数并且有一个参考

到WARC_Standard_Functions,它保存了日常功能并且有

引用Microsoft.Practices.EnterpriseLibrary.Data.dll和

Microsoft.Practices.EnterpriseLibrary.Common.dll


我希望MS Access 2003可以使用WARC_Subs_Reporting.dll和所以有

为上述所有人分配了强名称。我为WARC_Subs_Reporting.dll创建了一个安装

例程,然后将其他3个名为dll的

作为参考。运行时安装将所有4个dll'安装到正确的

目录。然后我将WARC_Subs_Reporting.dll添加到GAC,因为它是我从COM访问时唯一的

dll。


我现在已经创建了一个虚拟对象VB 2005项目测试已安装的dll。当我逐步执行
时,它调用WARC_Subs_Reporting.dll中的一个过程,

调用WARC_Standard_Functions中的一个过程,该过程使用

创建数据集DAAB内的程序。但是,它总是落在DAAB中的以下代码行之后的




返回EnterpriseLibraryFactory.BuildUp< T>(name,configurationSource); <

''NameTypeFactoryBase''类中的'public T Create(string name)''程序中的



给出这个错误:




的类型初始化程序''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''

抛出异常。


现在,说实话,我不知道这是什么,找不到任何有用的

帮助解决这个问题。任何想法。


谢谢


Chubbly

Now I''m coming from a VB6 background so I may be overlooking something here.

I have functionality that is contained with 2 VB 2005 dll''s.

WARC_Subs_Reporting.dll which handles report functions and has a reference
to WARC_Standard_Functions which holds the day to day functionality and has
references to Microsoft.Practices.EnterpriseLibrary.Data.dll and
Microsoft.Practices.EnterpriseLibrary.Common.dll

I want WARC_Subs_Reporting.dll available to MS Access 2003 and so have
assigned Strong Names to all of the above. I have created an install
routine for WARC_Subs_Reporting.dll which then has the other 3 named dll''s
as references. The install when run installs all 4 dll''s to the correct
directory. I then add WARC_Subs_Reporting.dll to the GAC as it is the only
dll I require to access from COM.

I''ve now created a dummy VB 2005 project to test the installed dll. When I
step through, it calls a procedure within WARC_Subs_Reporting.dll, which
calls a procedure within WARC_Standard_Functions that creates a dataset by
using the procedures within the DAAB. However, it always falls over on the
following line of code within the DAAB:

return EnterpriseLibraryFactory.BuildUp<T>(name, configurationSource);

within the ''public T Create(string name)'' procedure within the
''NameTypeFactoryBase'' class.

Giving this error:

The type initializer for
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''
threw an exception.

Now, to be honest, I have no idea what this is and cannot find any useful
help on the matter. Any ideas.

Thanks

Chubbly

推荐答案

很好,


你试过调试吗?异常的

Message属性中也应该有信息。另外,请务必检查

InnerException属性。看起来有一个静态构造函数用于

Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.EnterpriseLibraryFactory

类哪个抛出异常。


此外,对您的安装发表评论。虽然您可能只是从GAC中的一个程序集中公开

类,但您应该拥有程序集在GAC中的所有引用

。如果您知道

它将需要这些参考资料,那么只需要GAC中的一个程序集就可以了。

是非常有意义的。 />

这里的想法是将这些程序集作为逻辑单元分发,这是你目前正在分解的



将它们添加到GAC不会让它们对COM可见,它只会强制执行该逻辑单元。


希望这会有所帮助。


-

- Nicholas Paldino [.NET / C#MVP]

- mv*@spam.guard.caspershouse.com

" Chubbly Geezer" < CH ************ @ newsgroup.nospam>在消息中写道

新闻:OI ************** @ TK2MSFTNGP04.phx.gbl ...
Chubbly,

Have you tried to debug this? There should also be information in the
Message property of the exception. Also, be sure to check the
InnerException property. It looks like there is a static constructor for
the
Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.EnterpriseLibraryFactory
class which is throwing an exception.

Also, a comment on your installation. While you might only be exposing
classes from one assembly in the GAC, you should have all of the references
that the assembly has in the GAC as well. It doesn''t make sense to have
just the one assembly in the GAC and the others be private, when you know
that it will require those references.

The idea here is to distrubute those assemblies as a logical unit, which
you are currently breaking up.

Adding them to the GAC won''t make them visible to COM, it will just
enforce that logical unit.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Chubbly Geezer" <ch************@newsgroup.nospam> wrote in message
news:OI**************@TK2MSFTNGP04.phx.gbl...
现在我在来自VB6的背景,所以我可能会忽略这里的东西


我有2个VB 2005 dll包含的功能。

WARC_Subs_Reporting。处理报告功能的dll,以及对WARC_Standard_Functions的引用,其中包含日常功能,并且引用了Microsoft.Practices.EnterpriseLibrary.Data.dll和
Microsoft.Practices.EnterpriseLibrary。 Common.dll

我希望MS Access 2003可以使用WARC_Subs_Reporting.dll,因此为所有上述内容分配了强名称。我为WARC_Subs_Reporting.dll创建了一个安装
例程,然后将另外3个名为dll的
作为参考。运行时安装将所有4个dll安装到正确的
目录。然后我将WARC_Subs_Reporting.dll添加到GAC,因为它只是我从COM访问所需的dll。

我现在已经创建了一个虚拟的VB 2005项目来测试已安装的dll 。当我单步执行时,它会调用WARC_Subs_Reporting.dll中的一个过程,该过程调用WARC_Standard_Functions中的一个过程,该过程使用DAAB中的过程通过
创建数据集。但是,它总是落在DAAB中的以下代码行上:

返回EnterpriseLibraryFactory.BuildUp< T>(name,configurationSource);


''NameTypeFactoryBase''类中的'public T Create(string name)''程序。

给出此错误:

类型初始值设定项
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''
引发了一个例外。

现在,说实话,我不知道这是什么是的,也找不到任何有用的帮助。任何想法。

谢谢

Chubbly
Now I''m coming from a VB6 background so I may be overlooking something
here.

I have functionality that is contained with 2 VB 2005 dll''s.

WARC_Subs_Reporting.dll which handles report functions and has a reference
to WARC_Standard_Functions which holds the day to day functionality and
has references to Microsoft.Practices.EnterpriseLibrary.Data.dll and
Microsoft.Practices.EnterpriseLibrary.Common.dll

I want WARC_Subs_Reporting.dll available to MS Access 2003 and so have
assigned Strong Names to all of the above. I have created an install
routine for WARC_Subs_Reporting.dll which then has the other 3 named dll''s
as references. The install when run installs all 4 dll''s to the correct
directory. I then add WARC_Subs_Reporting.dll to the GAC as it is the
only dll I require to access from COM.

I''ve now created a dummy VB 2005 project to test the installed dll. When
I step through, it calls a procedure within WARC_Subs_Reporting.dll, which
calls a procedure within WARC_Standard_Functions that creates a dataset by
using the procedures within the DAAB. However, it always falls over on
the following line of code within the DAAB:

return EnterpriseLibraryFactory.BuildUp<T>(name, configurationSource);

within the ''public T Create(string name)'' procedure within the
''NameTypeFactoryBase'' class.

Giving this error:

The type initializer for
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''
threw an exception.

Now, to be honest, I have no idea what this is and cannot find any useful
help on the matter. Any ideas.

Thanks

Chubbly





企业库使用配置信息来建立它的连接

string。

看看这里。


您的配置信息可能已关闭/错误。

http://davidhayden.com/blog/dave/arc...1/08/2686.aspx


" Chubbly Geezer" < CH ************ @ newsgroup.nospam>在消息中写道

新闻:OI ************** @ TK2MSFTNGP04.phx.gbl ...

The enterprise library uses config information to build its connection
string.
Take a look here.

Your configuration information is probably off/wrong.

http://davidhayden.com/blog/dave/arc...1/08/2686.aspx


"Chubbly Geezer" <ch************@newsgroup.nospam> wrote in message
news:OI**************@TK2MSFTNGP04.phx.gbl...
现在我在来自VB6的背景,所以我可能会在这里忽略

我的功能包含2个VB 2005 dll'。

WARC_Subs_Reporting.dll处理报告函数并提供了WARC_Standard_Functions的参考,其中包含日常功能,
引用了Microsoft.Practices.EnterpriseLibrary.Data.dll和
Microsoft.Practices.EnterpriseLibrary.Common.dll

我希望MS Access 2003可以使用WARC_Subs_Reporting.dll,因此为所有上述内容分配了强名称。我为WARC_Subs_Reporting.dll创建了一个安装
例程,然后将另外3个名为dll的
作为参考。运行时安装将所有4个dll安装到正确的
目录。然后我将WARC_Subs_Reporting.dll添加到GAC,因为它是我需要从COM访问的
唯一的dll。

我现在已经创建了一个虚拟的VB 2005项目来测试已安装的dll 。当
我单步执行时,它调用WARC_Subs_Reporting.dll中的一个过程,该过程调用WARC_Standard_Functions中的一个过程,该过程使用DAAB中的过程通过
创建数据集。但是,它总是落在
DAAB中的以下代码行:

返回EnterpriseLibraryFactory.BuildUp< T>(name,configurationSource);


''NameTypeFactoryBase''类中的'public T Create(string name)''程序。

给出此错误:

类型初始值设定项

''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.En

terpriseLibraryFactory''抛出异常。

现在,到说实话,我不知道这是什么,也找不到任何有用的帮助。任何想法。

非常好

Now I''m coming from a VB6 background so I may be overlooking something here.
I have functionality that is contained with 2 VB 2005 dll''s.

WARC_Subs_Reporting.dll which handles report functions and has a reference
to WARC_Standard_Functions which holds the day to day functionality and has references to Microsoft.Practices.EnterpriseLibrary.Data.dll and
Microsoft.Practices.EnterpriseLibrary.Common.dll

I want WARC_Subs_Reporting.dll available to MS Access 2003 and so have
assigned Strong Names to all of the above. I have created an install
routine for WARC_Subs_Reporting.dll which then has the other 3 named dll''s
as references. The install when run installs all 4 dll''s to the correct
directory. I then add WARC_Subs_Reporting.dll to the GAC as it is the only dll I require to access from COM.

I''ve now created a dummy VB 2005 project to test the installed dll. When I step through, it calls a procedure within WARC_Subs_Reporting.dll, which
calls a procedure within WARC_Standard_Functions that creates a dataset by
using the procedures within the DAAB. However, it always falls over on the following line of code within the DAAB:

return EnterpriseLibraryFactory.BuildUp<T>(name, configurationSource);

within the ''public T Create(string name)'' procedure within the
''NameTypeFactoryBase'' class.

Giving this error:

The type initializer for
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.En
terpriseLibraryFactory'' threw an exception.

Now, to be honest, I have no idea what this is and cannot find any useful
help on the matter. Any ideas.

Thanks

Chubbly



Nicolas


感谢您的快速回复。


我无法找到有关内部异常的任何信息,但复制此错误

to剪贴板产生以下内容:


System.TypeInitializationException未处理

Message ="

'的类型初始化程序''Microsoft .Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''

抛出异常。"

Source =" Microsoft.Practices.EnterpriseLibrary.Comm on"

TypeName =" Microsoft.Practices.EnterpriseLibrary.Co mmon.Configuration.ObjectBuilder.EnterpriseLibrary Factory"

StackTrace:

at

Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.EnterpriseLibraryFactory.Bu ildUp [T](String

id,IConfigurationSource c onfigurationSource)



Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.NameTypeFactoryBase`1.Creat e(String

name)

at

Microsoft.Practices.EnterpriseLibrary.Data.Databas eFactory.CreateDatabase(String

name)

at SharedFunctions.clsConnection.CreateDataset(String strSQL,String

conn)

at WARC_Subs_Reporting.modRenewal.AgentsRenewalsCheck()

at WARC_Subs_Reporting.clsPublic.AgentsRenewal ()

在WindowsApplication3.Form1.Button1_Click(对象发送者,EventArgs

e)中的C:\ temp \ 20055 \ WindowsApplication3 \ WindowsApplicatio n3 \Form1。 vb:第8行

在System.Windows.Forms.Control.OnClick(EventArgs e)

在System.Windows.Forms.Button.OnClick(EventArgs e)

System.Windows.Forms.Control.WmMouseUp上的
(消息& m,MouseButtons

按钮,Int32点击)

在System.Windows.Forms.Control.WndProc(消息& m)

在System。 Windows.Forms.ButtonBase.WndProc(消息& m)

在System.Windows.Forms.Button.WndProc(消息& m)

at

System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message&

m)

在System.Windows.Forms.NativeWindow.DebuggableCallba ck(IntPtr hWnd,

Int32 msg,IntPtr wparam,IntPtr lparam)

在System.Windows.Forms.UnsafeNativeMethods.DispatchM essageW(MSG&

msg)

at

System.Windows.Forms.Application.ComponentManager 。 System.Windows.Forms.UnsafeNativeMethods.IMsoCompo nentManager.FPushMessageLoop(Int32

dwComponentID,Int32 reason,Int32 pvLoopData)

at

System.Windows .Forms.Application.ThreadContext.Run MessageLoopInner(Int32

reason,ApplicationContext context)

at

System.Windows.Forms.Application.ThreadContext .Run MessageLoop(Int32原因,

ApplicationContext上下文)

在System.Windows.Forms.Application.Run(ApplicationCo ntext context)

at

Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.OnRun()



Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.DoApplicationModel()<



Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.Run(String []

commandLine)
WindowsApplication3上的
.My.MyApplication.Main(String [] Args)

17d14f5c-a337-4978-8281-53493378c1071.vb:li在System.AppDomain.nExecuteAssembly(程序集程序,字符串[]

args)

在System.AppDomain.ExecuteAssembly(String assemblyFile)中的$ 81

,证据

assemblySecurity,String [] args)

at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()

at System.Threading .ThreadHelper.ThreadStart_Context(对象状态)

在System.Threading.ExecutionContext.Run(ExecutionCon文本

executionContext,ContextCallback回调,对象状态)

在System.Threading.ThreadHelper.ThreadStart()


,我完全迷失了。我可以看到错误发生的地方但是

不太确定如何解决。


Chubbly

" Nicholas Paldino [ .NET / C#MVP]" < mv*@spam.guard.caspershouse.com>写在

消息新闻:eo ************** @ TK2MSFTNGP03.phx.gbl ...
Nicolas

thanks for the quick response.

I am unable to find any info on the inner exception, but copying this error
to the clipboard produces the following:

System.TypeInitializationException was unhandled
Message="The type initializer for
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''
threw an exception."
Source="Microsoft.Practices.EnterpriseLibrary.Comm on"
TypeName="Microsoft.Practices.EnterpriseLibrary.Co mmon.Configuration.ObjectBuilder.EnterpriseLibrary Factory"
StackTrace:
at
Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.EnterpriseLibraryFactory.Bu ildUp[T](String
id, IConfigurationSource configurationSource)
at
Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.NameTypeFactoryBase`1.Creat e(String
name)
at
Microsoft.Practices.EnterpriseLibrary.Data.Databas eFactory.CreateDatabase(String
name)
at SharedFunctions.clsConnection.CreateDataset(String strSQL, String
conn)
at WARC_Subs_Reporting.modRenewal.AgentsRenewalsCheck ()
at WARC_Subs_Reporting.clsPublic.AgentsRenewal()
at WindowsApplication3.Form1.Button1_Click(Object sender, EventArgs
e) in C:\temp\2005\WindowsApplication3\WindowsApplicatio n3\Form1.vb:line 8
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at
System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message&
m)
at System.Windows.Forms.NativeWindow.DebuggableCallba ck(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchM essageW(MSG&
msg)
at
System.Windows.Forms.Application.ComponentManager. System.Windows.Forms.UnsafeNativeMethods.IMsoCompo nentManager.FPushMessageLoop(Int32
dwComponentID, Int32 reason, Int32 pvLoopData)
at
System.Windows.Forms.Application.ThreadContext.Run MessageLoopInner(Int32
reason, ApplicationContext context)
at
System.Windows.Forms.Application.ThreadContext.Run MessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationCo ntext context)
at
Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.OnRun()
at
Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.DoApplicationModel()
at
Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.Run(String[]
commandLine)
at WindowsApplication3.My.MyApplication.Main(String[] Args) in
17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[]
args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

with which I am totally lost. I can see where the error is happening but
not too sure how to resolve.

Chubbly
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:eo**************@TK2MSFTNGP03.phx.gbl...
Chubbly,

你试过调试吗?异常的
Message属性中也应该有信息。另外,请务必检查
InnerException属性。看起来有一个静态构造函数,用于
Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.EnterpriseLibraryFactory
类抛出异常。
另外,对您的安装发表评论。虽然您可能只是从GAC中的一个程序集中公开类,但您应该拥有该程序集在GAC中的所有引用。只知道GAC中的一个组件而其他组件是私有的,当你知道它需要那些参考时,它并没有意义。

这个想法这里是将这些程序集作为一个逻辑单元分发,你目前正在分手。

将它们添加到GAC不会让它们对COM可见,它只是
希望这会有所帮助。

-
- Nicholas Paldino [.NET / C#MVP]
- mv*@spam.guard.caspershouse.com

" Chubbly Geezer" < CH ************ @ newsgroup.nospam>在消息中写道
新闻:OI ************** @ TK2MSFTNGP04.phx.gbl ...
Chubbly,

Have you tried to debug this? There should also be information in the
Message property of the exception. Also, be sure to check the
InnerException property. It looks like there is a static constructor for
the
Microsoft.Practices.EnterpriseLibrary.Common.Confi guration.ObjectBuilder.EnterpriseLibraryFactory
class which is throwing an exception.

Also, a comment on your installation. While you might only be exposing
classes from one assembly in the GAC, you should have all of the
references that the assembly has in the GAC as well. It doesn''t make
sense to have just the one assembly in the GAC and the others be private,
when you know that it will require those references.

The idea here is to distrubute those assemblies as a logical unit,
which you are currently breaking up.

Adding them to the GAC won''t make them visible to COM, it will just
enforce that logical unit.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Chubbly Geezer" <ch************@newsgroup.nospam> wrote in message
news:OI**************@TK2MSFTNGP04.phx.gbl...
现在我来自VB6背景,所以我可能会忽略这里的东西


我的功能包含2个VB 2005 dll'。

WARC_Subs_Reporting.dll处理报告函数并具有对WARC_Standard_Functions的引用,该函数保存了日常功能,并且引用了Microsoft.Practices.EnterpriseLibrary.Data.dll和
Microsoft.Practices.EnterpriseLibrary。 Common.dll

我希望MS Access 2003可以使用WARC_Subs_Reporting.dll,因此为所有上述内容分配了强名称。我为WARC_Subs_Reporting.dll创建了一个安装
例程,然后将另外3个命名为
dll'作为引用。运行时安装将所有4个dll安装到
正确的目录中。然后我将WARC_Subs_Reporting.dll添加到GAC,因为它是我需要从COM访问的唯一DLL。

我现在已经创建了一个虚拟的VB 2005项目来测试已安装的dll 。当我单步执行时,它调用WARC_Subs_Reporting.dll中的一个过程,
调用WARC_Standard_Functions中的一个过程,该过程通过使用DAAB中的过程创建一个
数据集。但是,它总是落在DAAB中的以下代码行上:

返回EnterpriseLibraryFactory.BuildUp< T>(name,configurationSource);


''NameTypeFactoryBase''类中的'public T Create(string name)''程序。

给出此错误:

类型初始值设定项
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''
引发了一个例外。

现在,说实话,我不知道这是什么是的,也找不到任何有用的帮助。任何想法。

感谢

Chubbly
Now I''m coming from a VB6 background so I may be overlooking something
here.

I have functionality that is contained with 2 VB 2005 dll''s.

WARC_Subs_Reporting.dll which handles report functions and has a
reference to WARC_Standard_Functions which holds the day to day
functionality and has references to
Microsoft.Practices.EnterpriseLibrary.Data.dll and
Microsoft.Practices.EnterpriseLibrary.Common.dll

I want WARC_Subs_Reporting.dll available to MS Access 2003 and so have
assigned Strong Names to all of the above. I have created an install
routine for WARC_Subs_Reporting.dll which then has the other 3 named
dll''s as references. The install when run installs all 4 dll''s to the
correct directory. I then add WARC_Subs_Reporting.dll to the GAC as it
is the only dll I require to access from COM.

I''ve now created a dummy VB 2005 project to test the installed dll. When
I step through, it calls a procedure within WARC_Subs_Reporting.dll,
which calls a procedure within WARC_Standard_Functions that creates a
dataset by using the procedures within the DAAB. However, it always
falls over on the following line of code within the DAAB:

return EnterpriseLibraryFactory.BuildUp<T>(name, configurationSource);

within the ''public T Create(string name)'' procedure within the
''NameTypeFactoryBase'' class.

Giving this error:

The type initializer for
''Microsoft.Practices.EnterpriseLibrary.Common.Conf iguration.ObjectBuilder.EnterpriseLibraryFactory''
threw an exception.

Now, to be honest, I have no idea what this is and cannot find any useful
help on the matter. Any ideas.

Thanks

Chubbly




这篇关于DAAB问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆