S
S.Sigal
Hello:
Having trouble getting IDE to play nice/accept when designing Controls that need
helper classes...
I would like to compile controls as separate controls -- yet share some common
'helper' functions.
How can I set up -- or get the equivalent workability of --
CustomWebControl1\CustomWebControl1.sln
CustomWebControl2\CustomWebControl2.sln
CustomWebControl3\CustomWebControl3.sln
CustomCode\SharedCode.sln
I tried this approach, with SharedCode being a Project Dependancy for each of
the other three, and while that works in RunTime -- that fails in DesignTime
IDE. (It appears that when I add the Controls to the ToolBox the IDE copies the
dlls pointed to -- but not any dependancies (!!!) -- to another directory before
using it... In other words fails because it only has half of what it needs).
I understand that I could give SharedCode.dll a strong name and put it in the
GACL -- and that might be possible on my computer -- but be impossible to do
with site where I am hosted.(no access to GACL).
Right now, I am cut/copying the helper functions in between assemblies... which
is leading to it being hard to track down/correct bugs globally... And on top of
that -- the helper functions are not small so massive code bloat.
Anyone have an idea on how to make working on controls, without cut/pasting code
all over the place?
Thank you so much!
Sky
Having trouble getting IDE to play nice/accept when designing Controls that need
helper classes...
I would like to compile controls as separate controls -- yet share some common
'helper' functions.
How can I set up -- or get the equivalent workability of --
CustomWebControl1\CustomWebControl1.sln
CustomWebControl2\CustomWebControl2.sln
CustomWebControl3\CustomWebControl3.sln
CustomCode\SharedCode.sln
I tried this approach, with SharedCode being a Project Dependancy for each of
the other three, and while that works in RunTime -- that fails in DesignTime
IDE. (It appears that when I add the Controls to the ToolBox the IDE copies the
dlls pointed to -- but not any dependancies (!!!) -- to another directory before
using it... In other words fails because it only has half of what it needs).
I understand that I could give SharedCode.dll a strong name and put it in the
GACL -- and that might be possible on my computer -- but be impossible to do
with site where I am hosted.(no access to GACL).
Right now, I am cut/copying the helper functions in between assemblies... which
is leading to it being hard to track down/correct bugs globally... And on top of
that -- the helper functions are not small so massive code bloat.
Anyone have an idea on how to make working on controls, without cut/pasting code
all over the place?
Thank you so much!
Sky