web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Customizations Project...
Microsoft Dynamics CRM (Archived)

Customizations Project using new Dynamics Software Developer Toolkit - Am I doing something wrong?

(0) ShareShare
ReportReport
Posted on by Ben Walker 265

Using latest version of the toolkit.

Within an existing project, I create a new project of type 'Customizations Project'.

I then right-click on the project, select 'CRM -> Import from CRM' and the progress bar works its way to completion. I am then presented with a screen with the components it has found and wants to add to the project.

However, even with every single component selected, if I click 'OK' nothing happens. Nothing gets added to the project.

Eventually, I have no option but to click 'Cancel' and the window disappears, but still with nothing added to the project.

VS2015 Enterprise.

CRM 2015 On Prem.

Am I missing a step?

*This post is locked for comments

I have the same question (0)
  • Ben Walker Profile Picture
    Ben Walker 265 on at

    Just tried this on a machine with a previous version of the toolkit, and it works fine, but on 2 machines with the latest version of the toolkit, it does not work. Version 1.3.2000.8675 seems not to work - version 1.3.2000.8489 works OK.

  • MattB-MSFT Profile Picture
    MattB-MSFT on at

    When you click the ok button,  the items list should disappear.  when you click back on Visual Studio you will be presented with a "Reload Project" dialog,  when you click yes to that, it should reload the customizations project and show you the updated structure..  

    Is it not doing that?

    or did you do it once and your trying to add deltas ?

    thanks

    MattB.

  • Ben Walker Profile Picture
    Ben Walker 265 on at

    Hi Matt, no it's not doing that. Just sits there doing nothing.

    My earlier reply was not quite accurate.

    It seems as if it works in a newly created solution, but if you add customisation project to a solution built with an earlier release of the toolkit it does not work. That's as far as we've got in our investigations and I'll have to leave it there until next week, sorry.

  • MattB-MSFT Profile Picture
    MattB-MSFT on at

    Odd,  do you mean earlier release of the 1.3 toolkit right... not the old VS 2012 version.

    or did this solution start life in the 2012 version and you have updated it?

    MattB

  • Ben Walker Profile Picture
    Ben Walker 265 on at

    I mean an earlier release of the current toolkit.

    Although this solution did once have an old VS 2012 solution toolkit project, we branhced the code, delete the old projects, upgraded to VS2015 and then recreated the CRM Projects from scratch, so they should have no remnants of the old VS2012 toolkit.

    So I mean that the problem seems to happen when we try and a customisations project to a an existing project, but does not happen when we create a brand new solution with one in. More next week...

  • Ben Walker Profile Picture
    Ben Walker 265 on at

    Just to confirm the same behaviour on another PC.

    Adding a Customisations Project to an existing solution gives the error. Creating a brand new solution with a customisation project in it - no problem.

  • MattB-MSFT Profile Picture
    MattB-MSFT on at

    Ok, so lets try a few things when you can to try to narrow down the issue.

    First, can you make sure that there is a reference from the customization project in the CrmPackage Project,  if that is missing please add it and try again..

    If that does not work,  from the working project, in the customizations project there is a file called Microsoft.Crm.SolutionProjects.Metadata.targets,  Please verify that is in the 'broken' customizations project, if it is please copy the content from the working version to the broken version and try again.

  • Ben Walker Profile Picture
    Ben Walker 265 on at

    Hey Matt,

    I've worked out what the problem is and how to get round it.

    The unpacked solution items only get added to the project if your customisations project is in the root of the Visual Studio Project. If you have add the customisations project in a folder within the solution, when you click OK, nothing happens. Maybe it's trying to find the folder on disk, which won't actually exist.

    So I can easily get round this by putting the project in the root.

    There's another couple of issues which I've seen happen quite a few times while experimenting.

    When you first create a customisations project you get an error: "Reference project has some errors, please resolve those before referencing" and the referenced project shows up with a yellow exclamation mark in the CrmPackage project references.

    And when you try and build the solution, you get an error like this:

    The command "REM SET AssemblyVersionDefinitionFile=

             REM SET AssemblyVersionName=

             "\SupportLibs\CRMSDKBin\SolutionPackager.exe" -a:pack -z:"bin\Debug\CrmVSSolution2.CustomizationProject3.zip" -f:"obj\Debug\\BeforeLoc"" exited with code 3

    Anyway, have managed to resolve the most serious issue - will let you know if I can work out any more about the other two issues.

    Ben

  • MattB-MSFT Profile Picture
    MattB-MSFT on at

    We will get a fix out on this issue in a few days Ben,  the project is doing that as a side effect of how we do localization and we need to unwind that.

    The second issue is similar but will go away once you extract your solution once.  We will look at getting a longer term fix in for folks that will not cause that to appear on a empty project build.

  • Community Member Profile Picture
    Community Member on at

    Ben & Matt, 

    Any further update on the 

    The command "REM SET AssemblyVersionDefinitionFile=

             REM SET AssemblyVersionName=

             "\SupportLibs\CRMSDKBin\SolutionPackager.exe" -a:pack -z:"bin\Debug\CrmVSSolution2.CustomizationProject3.zip" -f:"obj\Debug\\BeforeLoc"" exited with code 3

    I am running into the same issue as well.  We dont need localization in our Solution, Does this build error stop the packaging of the solution or is just a post packaging Locatization Step. 

    Any insight in this will be very appreciated. 

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans