ConnectionStringName

[GoogleCodeExporter]

In discussions with Blake on the following 
post:http://community.codesmithtools.com/Template_Frameworks/f/66/p/12262/47357.
aspx#47357

He asked that I log this issue with your Tracker.

I would recommend that you add a "ConnectionStringName" property to you Edit 
Outputs interface.  Currently you use the "DatabaseName" return value from the 
dbProvider.  This is not always an accurate name.  When I want to change the 
connection string to point to a different database it now makes the name of the 
connection be inaccurate.  If my dev database is is name App_dev and my QA 
database is App_qa when I want to change the application to point to qa my 
"connection string" is still named App_dev.  Although this is harmless its just 
not very pretty.

Please let me know if you have any questions.

Thanks

dbl

Original issue reported on code.google.com by ibflyfis...@yahoo.com on 19 Oct 2011 at 4:09

[GoogleCodeExporter]

Original comment by bniemyjski on 19 Oct 2011 at 9:41

• Changed state: Accepted
• Added labels: Type-Enhancement, Framework-NHibernate, Framework-PLINQO, Framework-PLINQOEF, Framework-CSLA

[GoogleCodeExporter]

Hello,

After thinking this over for possible inclusion and reviewing the thread above. 
We've decided against implementing this feature in the current release or 
future release. We feel that if you are using a Microsoft's newly designed 
web.configs or http://msdn.microsoft.com/en-us/library/dd465326.aspx this 
should solve deployment issues.

The connecting string should never be regenerated over so adding this option 
would make it unnecessary. If we did add this option we would have the 
potential to delete connection strings that shouldn't be deleted.

Original comment by bniemyjski on 9 Mar 2012 at 1:25

• Changed state: WontFix
• Removed labels: Type-Enhancement