N
n_o_s_p_a__m
Ok, I have source code shared between 2 projects using links in VSS,
so we are compiling the same type information (classes, interfaces,
enums) into more than one assembly. This was done only by special
request of our client.
I am wondering if this is ok to do:
In AssemblyA: class1's methods returns myclass objects defined in
myclass.cs comiled into AssemblyX and referenced by project A.
(AssemblyA-->references-->AssemblyX-->contains-->myclass ; class1
methods-->returns-->myclass)
In AssemblyB: class2 declares objects of type myclass as return values
from calls to class1, except that in this case, class library B
references a different assembly (AssemblyY) which also has myclass.cs
compiled into it.
(AssemblyB-->references-->AssemblyY (and AssemblyA)-->AssemblyY also
contains-->myclass ; class2 calls class1-->returns-->myclass)
This seems to be causing some security issues.
Anyone know why and if this should/should not work?
-KJ
so we are compiling the same type information (classes, interfaces,
enums) into more than one assembly. This was done only by special
request of our client.
I am wondering if this is ok to do:
In AssemblyA: class1's methods returns myclass objects defined in
myclass.cs comiled into AssemblyX and referenced by project A.
(AssemblyA-->references-->AssemblyX-->contains-->myclass ; class1
methods-->returns-->myclass)
In AssemblyB: class2 declares objects of type myclass as return values
from calls to class1, except that in this case, class library B
references a different assembly (AssemblyY) which also has myclass.cs
compiled into it.
(AssemblyB-->references-->AssemblyY (and AssemblyA)-->AssemblyY also
contains-->myclass ; class2 calls class1-->returns-->myclass)
This seems to be causing some security issues.
Anyone know why and if this should/should not work?
-KJ