G
Guest
Hi!
I have a Web App developed for1.1. Now we migrated to 2.0. We have a base
library/dll used by few applications. When we started working with 2.0; we
started using the Middle-tier schema objects(rather strongly-typed objects
for the middle-tier) that .Net 2.0 allows to design using VS 2005 GUI
interface. I am refering to this blog post:
http://weblogs.asp.net/scottgu/archive/2006/01/15/435498.aspx.
The only caveat is VS 2005 GUI interface forces you to store the connection
string under <connectionStrings> section of the Web.config file. Now to use
the old code (1.1version); we have to duplicate storing the connectionStrings
in 2 places in Web.config file:
1. the old way of storing it under <appSettings>.
2. The new way of storing it under <connectionStrings>.
This is not acceptable as we have to update the connectionStrings in
multiple places. I was wondering if there is a work-around for this problem.
May be i could have over-looked something. Any help to solve this problem is
really appreciated.
the connectionString semantics also have changed. Now with 2.0; you need to
specify the assemblyName which invalidates the connectionString in 1.1. In
2.0 they use the new ProviderModel for connection string and it requires that
u mention the assemblyName.
I remember reading lot of articles on how to secure ur connection strings in
MSDN for 1.1, like stroing them in registry, encrypting. Now they change the
API completely. It is ridiculous.
-Thanks
Chak.
I have a Web App developed for1.1. Now we migrated to 2.0. We have a base
library/dll used by few applications. When we started working with 2.0; we
started using the Middle-tier schema objects(rather strongly-typed objects
for the middle-tier) that .Net 2.0 allows to design using VS 2005 GUI
interface. I am refering to this blog post:
http://weblogs.asp.net/scottgu/archive/2006/01/15/435498.aspx.
The only caveat is VS 2005 GUI interface forces you to store the connection
string under <connectionStrings> section of the Web.config file. Now to use
the old code (1.1version); we have to duplicate storing the connectionStrings
in 2 places in Web.config file:
1. the old way of storing it under <appSettings>.
2. The new way of storing it under <connectionStrings>.
This is not acceptable as we have to update the connectionStrings in
multiple places. I was wondering if there is a work-around for this problem.
May be i could have over-looked something. Any help to solve this problem is
really appreciated.
the connectionString semantics also have changed. Now with 2.0; you need to
specify the assemblyName which invalidates the connectionString in 1.1. In
2.0 they use the new ProviderModel for connection string and it requires that
u mention the assemblyName.
I remember reading lot of articles on how to secure ur connection strings in
MSDN for 1.1, like stroing them in registry, encrypting. Now they change the
API completely. It is ridiculous.
-Thanks
Chak.