I believe I found where the problem lies! according to the my research, other programmers say that if you have too many properties and serializeable classes with those properties in you class library project, then you encounter with that slow typing problem.
my class library has about 20 client side webservice interface. so each of them has between 5-15 serializable classes which I generate using xsd.exe. Beside that there are like over 50 common manually made object classes with several properties. Do you think
that is really the problem? what would be the solution? should I create 20 class libraries for each client side webservice interface. that will make 20dlls for my website. using too many dlls as reference? is that advantage or disadvantage? please let me know.
emil_bg
Member
26 Points
50 Posts
Re: sub projects(class library) coding too slow
Sep 15, 2010 04:00 PM|LINK
I believe I found where the problem lies! according to the my research, other programmers say that if you have too many properties and serializeable classes with those properties in you class library project, then you encounter with that slow typing problem. my class library has about 20 client side webservice interface. so each of them has between 5-15 serializable classes which I generate using xsd.exe. Beside that there are like over 50 common manually made object classes with several properties. Do you think that is really the problem? what would be the solution? should I create 20 class libraries for each client side webservice interface. that will make 20dlls for my website. using too many dlls as reference? is that advantage or disadvantage? please let me know.
thanks
</div> </div>