StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODebugging x86 .NET application on Windows x64 in VS2008
primarykey
Id
2014734
data
AcceptedAnswerId
2084885
AnswerCount
3
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2010-01-06T17:10:54.967
FavoriteCount
0
LastActivityDate
2015-03-02T16:35:25.653
LastEditDate
2017-05-23T12:19:37.127
LastEditorUserId
-1
OwnerUserId
244805
ParentId
0
PostTypeId
1
Score
5
ViewCount
4727
LastEditorDisplayName
text
Body
I use the x64 version of Windows 7. My application use some COM servers (usual native x86 COM Servers) that can't be loaded in x64 context. So I decided run it as a x86 application using <a href="http://en.wikipedia.org/wiki/WOW64" rel="nofollow noreferrer">WOW</a> so I set platform target as x86. But Visual Studio 2008 debugger started to show messages like "The source file is different...." for all source files when I try debug it. What is reason for this behaviour? This question was born there <a href="https://stackoverflow.com/questions/2013943/the-source-file-is-different-message-in-visual-studio-2008-is-result-of-deb">"The source file is different...." message in Visual Studio 2008 is result of debugging x32 apps on x64 Windows</a> Update: I cleaned solution, rebuilt solution, removed obj, bin and etc. folders, restarted computer, reinstalled Visual Studio... So, what else could be the problem? Update2: If you create new Windows Application project and change target platform to x86 you will see this trouble. But if you delete Settings1.settings from project the trouble will be eliminated!!. Any Idea? Update3: <a href="http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/bc297668-65b4-46e8-969e-c7a6340d33b6" rel="nofollow noreferrer">http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/bc297668-65b4-46e8-969e-c7a6340d33b6</a>
Tags
<c#><visual-studio><debugging><visual-studio-2008><64bit>
Title
Debugging x86 .NET application on Windows x64 in VS2008
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USDmitry Borovsky
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODebugging x86 .NET application on Windows x64 in VS2008
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PODebugging x86 .NET application on Windows x64 in VS2008
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PODebugging x86 .NET application on Windows x64 in VS2008
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.