Dll Hell: It's still a problem in .NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello All:

I am about to revert to 100% native code over this. I have an application
that works fine under emulation. It includes a custom assembly with a button
subclass that does some neato things for my app. When I build and deply this
to the PocketPC device and run, I get some Could not load type
System.Windows.Forms.Control from assembly System.Windows.Forms. This seems
completely bogus to me. Does anyone know what the remedy is?

Robert
 
Robert,

Do you have the source to the control? Where does that assembly get
installed? I agree the message probably isn't telling you the real problem.

Ginny Caughey
..NET Compact Framework MVP
 
I do. It's a control library that I created.

It turns out that the smart device app when created added references to the
desktop versions of System.Windows.Forms and System.Drawing for some reason.
Once I manually set these to the .NETCF versions, all was fine.
 
Ah. Glad you got it worked out.

Ginny

Robert Burdick said:
I do. It's a control library that I created.

It turns out that the smart device app when created added references to
the
desktop versions of System.Windows.Forms and System.Drawing for some
reason.
Once I manually set these to the .NETCF versions, all was fine.



Ginny Caughey said:
Robert,

Do you have the source to the control? Where does that assembly get
installed? I agree the message probably isn't telling you the real
problem.

Ginny Caughey
..NET Compact Framework MVP

"Robert Burdick [eMVP]" <[email protected]>
wrote
in message news:[email protected]...
Hello All:

I am about to revert to 100% native code over this. I have an
application
that works fine under emulation. It includes a custom assembly with a
button
subclass that does some neato things for my app. When I build and
deply
this
to the PocketPC device and run, I get some Could not load type
System.Windows.Forms.Control from assembly System.Windows.Forms. This
seems
completely bogus to me. Does anyone know what the remedy is?

Robert
Click to expand...
Click to expand...
Click to expand...
 
Hi,

Can you give me more details around how you encountered this problem. It
would be really helpful if you can file a bug in LadyBug around this. I
suspect that this is a known issue that we are looking at - but can't tell
without more details

--
Thanks,
Sriram Krishnan
Program Manager, Visual Studio for Devices

This posting is provided "AS IS" with no warranties, and confers no rights.
Robert Burdick said:
I do. It's a control library that I created.

It turns out that the smart device app when created added references to
the
desktop versions of System.Windows.Forms and System.Drawing for some
reason.
Once I manually set these to the .NETCF versions, all was fine.



Ginny Caughey said:
Robert,

Do you have the source to the control? Where does that assembly get
installed? I agree the message probably isn't telling you the real
problem.

Ginny Caughey
..NET Compact Framework MVP

"Robert Burdick [eMVP]" <[email protected]>
wrote
in message news:[email protected]...
Hello All:

I am about to revert to 100% native code over this. I have an
application
that works fine under emulation. It includes a custom assembly with a
button
subclass that does some neato things for my app. When I build and
deply
this
to the PocketPC device and run, I get some Could not load type
System.Windows.Forms.Control from assembly System.Windows.Forms. This
seems
completely bogus to me. Does anyone know what the remedy is?

Robert
Click to expand...
Click to expand...
Click to expand...
 
Back
Top