Skip to main content

dll reference missing or XML namespace error–when using TFS

I don’t have a proper title for this blog post. But hopefully it helps someone when they google it.
When you use TFS for your development you may get weird compile errors where c# code can not be referenced. Namespace error.
Or visual studio projects won’t open because of XML namespace issue.
below is the error you get if you are trying to Edit a visual studio analysis project from the AOT.
The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\Users\munib\Documents\TFSAXDaxeam\Andromeda\Trunk\AX\EAM\Visual Studio Projects\Analysis Services Projects\Daxeam\Daxeam.dwproj
I did some digging around and found that the ProjectTypeGUID is blank. A GUID is not assigned to it.
Each of the visual studio AOT elements is assigned a GUID depending on what type it is.
With some of the visual studio elements, like c# projects. You can export the xpo, set the property in notepad and then import it.
Some like the Visual Studio Analysis Projects, you wont be able to import the xpo. This just errors out.
So, I wrote a job for this.

static void setAOTPropertyWithOutValidation(Args _args)
    TreeNode    treeNode;   treeNode = TreeNode::findNode(#VSProjectsAnalysisPath + '\\' + 'Daxeam');   if (treeNode)
        treeNode.AOTsetProperties('PROPERTIES\n ' + #PropertyProjectTypeGUID + '  #' + 
                        '{D2ABAB84-BF74-430A-B69E-9DC6D40DDA17}' + '\n ENDPROPERTIES\n');

Final result should be like so. Then all should be fine from here.


I got a Microsoft KB - not a general release. You have to request it.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi