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.
2014-01-31_1504
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="http://schemas.microsoft.com/developer/msbuild/2003" 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.
2014-01-31_1510
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)
{
    #AOT
    #Properties
    TreeNode    treeNode;   treeNode = TreeNode::findNode(#VSProjectsAnalysisPath + '\\' + 'Daxeam');   if (treeNode)
    {   
        treeNode.AOTsetProperties('PROPERTIES\n ' + #PropertyProjectTypeGUID + '  #' + 
                        '{D2ABAB84-BF74-430A-B69E-9DC6D40DDA17}' + '\n ENDPROPERTIES\n');
        treeNode.AOTsave();
    }
}


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

2014-01-31_1513


Updated:
I got a Microsoft KB - not a general release. You have to request it.
KB2926352/6.2.1000.5979
Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

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.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {    ...
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more