G
General Chaud Caliente
I am working on a .NET component library and I am trying to figure out
how to segregate designtime code from the runtime assembly. Delphi made
this easy.
My natural inclination is to put all of the designtime source files into
their own namespace and drop them into a sub-folder under the main
source folder. Then create a design project which contains all of the
runtime code, as well as all of the designtime code. The runtime
assembly would be called whatever.dll and the designtime assembly would
be called design.whatever.dll. All of that is easily done.
The problem is instructing the compiler to substitute the runtime
assembly for the assembly which was used at compile time.
In the compact framework, there is an attribute called "RuntimeAssembly"
that instructs the compiler to deploy another assembly to the device.
This is absolutely necessary in the compact framework, but also
desirable in the full framework.
If anyone out there has an idea on how to target a different assembly at
runtime, I'd sure be happy to hear about it.
--
With Regards,
General Chaud Caliente
www.ScaryShark.com
Note: My email address is spam proofed. Replace _spam@proofing_ with @.
how to segregate designtime code from the runtime assembly. Delphi made
this easy.
My natural inclination is to put all of the designtime source files into
their own namespace and drop them into a sub-folder under the main
source folder. Then create a design project which contains all of the
runtime code, as well as all of the designtime code. The runtime
assembly would be called whatever.dll and the designtime assembly would
be called design.whatever.dll. All of that is easily done.
The problem is instructing the compiler to substitute the runtime
assembly for the assembly which was used at compile time.
In the compact framework, there is an attribute called "RuntimeAssembly"
that instructs the compiler to deploy another assembly to the device.
This is absolutely necessary in the compact framework, but also
desirable in the full framework.
If anyone out there has an idea on how to target a different assembly at
runtime, I'd sure be happy to hear about it.
--
With Regards,
General Chaud Caliente
www.ScaryShark.com
Note: My email address is spam proofed. Replace _spam@proofing_ with @.