mydll.dll.config issues...

[huntco@gmail.com]

VS2005, .Net 2.x

I've built a .dll from the classlibrary template. Everything works
great on the development box. When moving it over to the production
box, I started getting database connection errors. Added some debug
code, and it looks like the connection string stored in the
application settings (app.config) are being compiled into the .dll
rather than being read into it from the accompanying mydll.dll.confi g
file at runtime.

I've seen several posts suggesting ways around this; I guess I'm not
proficient enough in VB.Net yet to "get it."

1) Is the "compiled in when it's a .dll, read in when it's an .exe" a
feature or a bug?
2) Since the item in question is a database (SQL) connection string
(required for the IDE to work when visually building tables,
tableadapters, methods on those tableadapters, etc.) - and that's
generaded by an IDE wizard and stored in the app.config file - how do
you get VB to:
a) recognize a valid connection string for the IDE environment and
b) change that string after it becomes "hard coded" by the .dll
build process?

[Patrice]

Re: mydll.dll.confi g issues...

Not sure what you mean especially with the first question.

IMO the problem is likely that you have actually AFAIK no dll.config file.
Settings are read in the *application* configuration file that is the
app.exe.config file...

---
Patrice

<huntco@gmail.c oma écrit dans le message de news:
1187786007.3071 47.196680@i13g2 00...legr oups.com...

VS2005, .Net 2.x
>
I've built a .dll from the classlibrary template. Everything works
great on the development box. When moving it over to the production
box, I started getting database connection errors. Added some debug
code, and it looks like the connection string stored in the
application settings (app.config) are being compiled into the .dll
rather than being read into it from the accompanying mydll.dll.confi g
file at runtime.
>
I've seen several posts suggesting ways around this; I guess I'm not
proficient enough in VB.Net yet to "get it."
>
1) Is the "compiled in when it's a .dll, read in when it's an .exe" a
feature or a bug?
2) Since the item in question is a database (SQL) connection string
(required for the IDE to work when visually building tables,
tableadapters, methods on those tableadapters, etc.) - and that's
generaded by an IDE wizard and stored in the app.config file - how do
you get VB to:
a) recognize a valid connection string for the IDE environment and
b) change that string after it becomes "hard coded" by the .dll
build process?
>