visual studio 2013 - Remote debugging Ax 2012 IL code -


i'm trying remote debugging working aos. breakpoints never hit due symbols not being loaded.

'ax32serv.exe' (clr v4.0.30319: x++ il app domain): loaded 'd:\program files\microsoft dynamics ax\60\server\myaos\bin\xppil\dynamics.ax.application.dll423.netmodule'. cannot find or open pdb file.

i have debugging symbols setup to:

\server\d$\program files\microsoft dynamics ax\60\server\myaos\bin\xppil

but visual studio never loads symbols cache.

  • i'm running visual studio administrator
  • my client configuration settings linked correct aos
  • i'm connecting aos aos-account
  • i'm local administrator on aos server
  • debugging options checked on server configuration

any idea i'm missing or not doing correctly?

procmon telling me devenv.exe process can't access below path (path_not_found). i'm clueless on why it's trying access path.

\server\d$\program files\microsoft dynamics ax\60\server\myaos\bin\xppil\dynamics.ax.application.dll33.pdb\63a38861ab9b4e6ea55578a367a991ad1\dynamics.ax.application.dll33.pdb

according experience deployment of assemblies hinders proper use of remote debugger @ aos side.

the following steps didn't in circumstances:

  • vs symbol cache set local path pdb files (vs @ remote box caches project aot).
  • vs symbol cache set shared folder (aos pdb files exposed network).
  • attempts find proper order of aos restart / clean debug information in order sync versions of loaded dll , loaded pdb.
  • aos option "assembly hot-swap" didn't either. works, pdb , dll not in sync.
  • tinkering dl3 / vsassemblies aos folders didn't reveal workarounds.

eventually found possible way overcome "missing symbol information" message root cause here in opinion. there couple vs projects residing @ aot subject remote debugging. every attempt showed no luck due same "missing symbol information" error.

i hope following scenario op find solution aif web service:

  1. append csproj manifest following lines:

    <vsprojectoutputfiles include="$(outputpath)$(assemblyname).pdb">      <visible>true</visible> </vsprojectoutputfiles> 

    this helps save pdb artifacts aot tree.

  2. compile vs project @ morphx ide. compilation of project @ aot essential here, deploys matching pdb alongside dll.

  3. restart aos. hot-swap didn't worked pdb, restart mandatory here. result can see proper pdb within "modules" window @ vs , breakpoints reachable fact.

although using remote debugger looks appropriate aos (not bloat server dev tools), seems there still kinks in relation aos code deployment.


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

css - Make div keyboard-scrollable in jQuery Mobile? -

ruby on rails - Seeing duplicate requests handled with Unicorn -