i have use your scripts as u describe and succefully rebuild sources but when i open VS IDE a popup message box says
The following module was built either with optimizations enabled or without debug information:
To debug this module, change its project build configuration to Debug mode. To suppress this message, disable the 'Warn if no user code on launch' debugger option.
of course i can not dig into expressapp sources automatically only when i load symbols manually .
that is not the case with DxExpirience . there symbols work as expected.
am i missing something.
To solve this problem, you should remove the following line from the buildall.cmd file:
rd /S /Q %TempDir%
As you see this line removes a temporary directory where the sources were built. Now, this directory won't be removed and you will track the number of such directories each time you are going to rebuild our sources.
i m still expirience a undesirable debugging experience.
for xaf assemblies the debug symbols are loaded from a temp path(see exressApp.jpg) but for component assembiles from Program Files path (see xpo.jpg).
How can i make all symbols to load from Program Files path ?
Unfortunately, we do not a good solution here.
The main reason for moving the sources in a temporary folder is the fact that Visual Studio cannot build a solution if it contains items with long names. This is the case when building XAF from the Program Files folder. This is a limitation of the IDE, and we cannot bypass it on our side. The only way is to build from a folder that has a short name, for instance, from a folder in the root disc directory.
Is it a real problem for you to see that symbols are not loaded from the Program Files?
Thanks for the update. I have already explained the limitation of the msbuild that forced us to build the sources from a folder placed within the root disc folder. As I already said, we cannot bypass it on our side because this is not a DX problem.
Honestly, I do not see any reason of why resharper cannot work in this situation. Anyway, this is a problem of this tool itself.
I understand that this tool is important to you, but, unfortunately, we cannot bypass this limitation ourselves due to the objective reasons mentioned above. The only thing we can suggest you is to modify our build scripts, so that the sources are built not from a temporary folder (because I think this is the cause why the resharper doesn't work), but from a fixed folder in the root directory. For instance, we traditionally keep our sources by using the following path template: D:\2009.2\XAF\
Regarding alternatives, I have one, but I assume you won't like it. We have our own set of IDE Productivity Tools for Visual Studio. Thanks for understanding.
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.