using ExitoConsulting.Plugins.Base;
using Microsoft.Xrm.Sdk;
namespace ExitoConsulting.Plugins
{
public class OwnerSetName : SetNamePluginBase
{
protected override string GetName(Entity entity, IPluginExecutionContext context, IOrganizationService service)
{
var fullName = entity.GetAttributeValue("ec_fullname");
var clientId = entity.GetAttributeValue("ec_clientid");
if(string.IsNullOrEmpty(fullName))
{
return null;
}
var name = fullName;
if(!string.IsNullOrEmpty(clientId))
{
name = name + string.Format(" - {0}", clientId);
}
return name;
}
}
}
This add-on will be useful for each Microsoft Dynamics CRM Developer. It allows to initiate upload and publish process directly from Visul Studio. The main benefit is that web resources upload and publish process takes as little time as possible because add-on is only take care about web resources that are changed. It will help to speed up development and debugging processes by allowing you to focus on the code you are crating.
See full description here: http://happycrm.blogspot.ru/p/crm-publisher.html
If you have any issue or comment just write me in comments or you can also leave a feedback on Codeplex or Visual Stuio Gallery and I will fix it shortly.
Hope you will love this add-on.
Today I want to share how I organize Visual Studio Solution for small and medium size Microsoft Dynamics CRM implementation projects. For big projects solutions' structures are different and significantly depend on projects.
Below you can find common structure of a solution:
It doesn't mean that all solutions I did have the same structure. But all solutions have some or all projects from the list. Some solutions have even more projects.
Let me describe each project and folder one by one.
Let's go throw Custom Workflow Activity creation process today.
To do that I need following:
1. Open Visual Studio and create new “Class Library” project
2. Add Reference
Press Add New Reference:
