G
Guest
Okay, I would like to try converting our asp.net solution to 2.0.
Our current vs.net 2003 solution has about 25 projects (all c# library, as
we did not want to deal with the frontpage extensions). The final product is
an asp.net website. Each project is an asp.net application or just a C#
library (eg. businesslayer, datalayer etc.)
From the documentation I see that VS.Net 2005 is quite capable of converting
all our existing code. However, I am concerned that it will get rid of the
projects and combine everything into one big (and happy!) solution. I do not
want it done in this way!!!
I would like to keep these projects as separate dlls in a single solution
(if possible). This allows us to reuse some dlls in another solution (by
referencing the dlls).
Any ideas or advice? Should I manually do this without using the conversion
tool (there are about 1000+ files). Any pointer to any article/blogs will be
good.
Thanks
jojobar
-jojobar
Our current vs.net 2003 solution has about 25 projects (all c# library, as
we did not want to deal with the frontpage extensions). The final product is
an asp.net website. Each project is an asp.net application or just a C#
library (eg. businesslayer, datalayer etc.)
From the documentation I see that VS.Net 2005 is quite capable of converting
all our existing code. However, I am concerned that it will get rid of the
projects and combine everything into one big (and happy!) solution. I do not
want it done in this way!!!
I would like to keep these projects as separate dlls in a single solution
(if possible). This allows us to reuse some dlls in another solution (by
referencing the dlls).
Any ideas or advice? Should I manually do this without using the conversion
tool (there are about 1000+ files). Any pointer to any article/blogs will be
good.
Thanks
jojobar
-jojobar