AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 16.03.2012, 23:12   #1  
Blog bot is offline
Blog bot
Участник
 
25,459 / 846 (79) +++++++
Регистрация: 28.10.2006
emeadaxsupport: In Microsoft Dynamics AX 2012, compiler output setting of Message Window may cause errors when generating (incremental) CIL
Источник: http://blogs.msdn.com/b/axsupport/ar...ental-cil.aspx
==============

We are currently using AX 2012 CU-2. We came across an issue whereby generating CIL in a specific scenario caused some errors to be generated which did not help us to understand the cause of the issue.

In AX 2012 client, under menu File\Tools\Options, click on Development on left hand side and than the Compiler tab. In here you can change the default compiler output from “Form” to “Message Window”. This setting does not only effect the AX X++ compiler but also the output of the CIL compiler/generator as I found today.



When generating (incremental) CIL it’s required the X++ code compilation has first finished compiling without errors. However if you sometimes start CIL generation on a system where there still exits X++ compilation errors and with the compiler output setting set to “Message Window” than you get an error which may be confusing (see screenshot below) .



In the code snipett screenshot (given write at the bottom) where I added an X++ error to the class you can see by the icon in the AOT in front of the changed method there’s an error (top most dot is read; Green bottom dot means compiled without errors)


When now generating Incremental CIL I get the error below in the info log window. (No Messages get logged to the compiler output window)





Furthermore, generating CIL hereafter will hang the AOS (even if you have switched back the compiler output setting to “Form”) until the AOS service has been restarted.



WORKAROUND

We worked around by keeping the Compiler output settings to its default setting “Form”. With this setting generating CIL will report the X++ errors in the output dialog at the bottom of the screen, and the info log provides a meaningful error (See print screen below) and you can repeat generating CIL without AOS restart.







--author:Jago van der Most






Источник: http://blogs.msdn.com/b/axsupport/ar...ental-cil.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
emeadaxsupport: 3. Solving Fill Utility errors on Microsoft Dynamics AX 2012 - Error executing code: Wrong argument types for comparison Blog bot DAX Blogs 1 08.02.2012 08:53
rumicrosofterp: Dynamics AX на Convergence 2012 Blog bot Microsoft и системы Microsoft Dynamics 0 13.01.2012 11:11
AIF: Microsoft Dynamics AX 2012 Services and AIF White Papers Blog bot DAX Blogs 0 16.06.2011 00:11
dynamics-ax: Interview with Microsoft's Lachlan Cash on his new role, AX 2012 and more Blog bot DAX Blogs 6 22.04.2011 14:55
dynamics-ax: Microsoft Dynamics AX 2012, OData and EDM Blog bot DAX Blogs 0 02.02.2011 07:11
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 21:48.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.