Placing a control on a form causes an error

  • Thread starter Thread starter Just Me
  • Start date Start date
J

Just Me

Sometime when I place my usercontrol on a form I get a message that it can't
find a file that is referenced. The file is the only C# file in the solution
(say Library.DLL) .

I just noticed that the C# bin folder has a Debug and Release Folders which
contain Library.DLL, while vb bin contains Library.DLL.
Also, the file in question is the first file in the build sequence.
Also, that library shares a namespace with a VB library which inherits from
the C# library.

It's a real time waster. When it happens I close IDE, search and find all
the Library.DLL, delete them. Open Ide, rebuild and then I can continue.

I have no idea how to debug this. Any ideas??

Thanks
 
Is this on new or existing projects which contain this library ?
--
OHM ( Terry Burns ) * Use the following to email me *

Dim ch() As Char = "ufssz/cvsotAhsfbuTpmvujpotXjui/OFU".ToCharArray()
For i As Int32 = 0 To ch.Length - 1
ch(i) = Convert.ToChar(Convert.ToInt16(ch(i)) - 1)
Next
Process.Start("mailto:" & New String(ch))
 
I've been working on these projects, including the library, for about a year
and have been putting up with this problem for a very long time.

I've asked for help before but I guess nobody knows what's wrong.

Thanks for the interest.
 
Just a suggestion. Delete the reference in your project to the Library.dll.
Delete all Library.Dll's. Recompile the c# Lbrary source code in the debug
mode. That should put the Library.Dll in the C# debug folder. Next open
your project and create a reference to that Library.Dll. At least that will
eliminate the C# Release version. The Library.dll should also show up in
your vb project bin folder after you rebuild the vb project.
 
I just noticed that in C# project properties I can make the dll go into bin
for both the release and debug versions. I don't know if that makes any
difference to anything.

Maybe I could do what you suggest but use the bin directory so the dll will
be there for both versions. Do you have any ideas.

Thanks
 
I would just try the debug version first after deleting all the .dll's. If
that works, you could then try the other. Note that when you create a
reference to the .dll in your vb.net project, it will copy and keep the
latest version of the Library.dll in the vb.net project bin directory.
However, everytime you build your Vb.Net project, it will get the latest
version of the Library.dll that was referenced and copy it to the Vb.Net
project bin directory.
 
Thanks a lot

Dennis said:
I would just try the debug version first after deleting all the .dll's. If
that works, you could then try the other. Note that when you create a
reference to the .dll in your vb.net project, it will copy and keep the
latest version of the Library.dll in the vb.net project bin directory.
However, everytime you build your Vb.Net project, it will get the latest
version of the Library.dll that was referenced and copy it to the Vb.Net
project bin directory.
Click to expand...
 
Back
Top