StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POVS2010 debug/release.config not working
primarykey
Id
7485652
data
AcceptedAnswerId
7495905
AnswerCount
2
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-20T13:08:36.483
FavoriteCount
2
LastActivityDate
2014-03-26T12:13:13.387
LastEditDate
2014-03-26T12:13:13.387
LastEditorUserId
1474519
OwnerUserId
954725
ParentId
0
PostTypeId
1
Score
2
ViewCount
5571
LastEditorDisplayName
text
Body
I'm having a bit of trouble with my <code>web.debug.config</code> and <code>web.release.config</code> files. To be more specific, my webpage will only use the default <code>web.config</code> file, and completely ignore the <code>debug</code> and <code>release</code> files. This happens not only when I run the project locally, but also when I publish it to an IIS server. I am using Visual Studio 2010 Ultimate (no Service Pack). Here are the config files: <code>web.config</code>: <pre class="lang-xml prettyprint-override"><code><?xml version="1.0"?> <configuration> <connectionStrings> <add name="MyConn" connectionString="SomeConnectionString" providerName="System.Data.SqlClient"/> </connectionStrings> </configuration> </code></pre> <code>web.debug.config</code> and <code>web.release.config</code>: <pre class="lang-xml prettyprint-override"><code><?xml version="1.0"?> <configuration xmlns:xtd="http://schemas.microsoft.com/XML-Document-Transform"> <connectionStrings> <add name="MyConn" connectionString="SomeOtherConnectionString" providerName="System.Data.SqlClient" xtd:Transform="Replace" xtd:Locator="Match(name)"/> </connectionStrings> </configuration> </code></pre> As I mentioned before, the website uses the connection string from the <code>web.config</code> file, and not from the <code>web.release.config</code>. Another interesting point is that in the physical folder to which I published the project, all three <code>config</code> files exist; each exactly the same as they appear in the VS solution. Suggestions, anyone?
Tags
<visual-studio-2010><web-config>
Title
VS2010 debug/release.config not working
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USjcjr
UserOwnerUserId
1. USYehuda Shapira
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POVS2010 debug/release.config not working
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POVS2010 debug/release.config not working
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POVS2010 debug/release.config not working
 UserUserId
 USDevDave
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.