Don't even try to put it in that folder.
..net assemblies are referenced from two places. #1 the folder in which the
application is stored and #2 the Global Assembly Cache or GAC.
If you're DLL is specialized for your application and unlikely to be useful
to other applications and deploy it into the folder where the executable is
to be stored. If your DLL is likely to be shared by several applications or
requires some strict version management then put it into the GAC. The
assemblies placed into the global assembly cache must be strongly named.
Your control probably falls into the latter category.
--
Bob Powell [MVP]
Visual C#, System.Drawing
The Image Transition Library wraps up and LED style instrumentation is
available in the June of Well Formed for C# or VB programmers
http://www.bobpowell.net/currentissue.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/gdiplus_faq.htm
The GDI+ FAQ RSS feed:
http://www.bobpowell.net/faqfeed.xml
Windows Forms Tips and Tricks RSS:
http://www.bobpowell.net/tipstricks.xml
Bob's Blog:
http://bobpowelldotnet.blogspot.com/atom.xml
"AA" <aa@hotmail.com> wrote in message
news:uC**************@TK2MSFTNGP10.phx.gbl...
Hi all,
I have created a .Net control for myself, and put it inside the folder
"framework\v1.1.4322".
Then, I create a new project, reference the dll and draw the control on
the window form.
I am fail running the project and the error is encountered at the line
"InitializeComponent" in the form, claiming that some dependency is
missing.
However, once putting the dll outside the folder "framework\v1.1.4322",
everythings go normal.
Do anyone have idea for that?
Thanks in advance!
Richard