I'm trying to customize the Dynamics GP using the Visual Studio. I got the VS Tools SDK installed on my system, But i'm unable to find the dynamics gp icon in the project templates.
How should integrate the VS Tools SDK with the VS 2010.
Thanks in advance.
Reinstall the SDK, and carefully read the Visual Studio versions. You won't get the templates on any version of VS after the GP date. In other words, for GP 2016, you have to use VS 2015 or earlier
http://dynDeveloper.com/Article/FD27
Related
I have installed Visual Studio 2015 (Professional). But when I open SharePoint 2010 project on VS 2015, it's showing project is incompatible.
Could you please tell any solution or idea to load the project in VS 2015?
Your project is not loading because Microsoft Office Developer Tools is not installed on your machine. You can easily modify your visual studio 2015 by following steps:
Run Visual Studio 2015 Setup File
Click on modify
Find the “Microsoft Office Developer Tools” and select it.
Finally click on Update.
After completing the setup open your project.
When you install VS2015, you do not install the mandatory Office Development Tools for Visual Studio 2015.
Once, you have downloaded and installed those. (Around 78MB) your SharePoint projects should, once again, load up without any errors.
Direct Link to the latest version:
http://aka.ms/getlatestofficedevtools
Just updated visual studio 2015, and I have a solution that has an API using azure tools v2.6, the update for visual studio had me install v2.7 azure tools.
I cannot convert the outdated project to v2.7 as it is asking me to, and 2.6 is not compatible with vs 2015. I need to access this project and continue working on it.
Anyone have this issue? Know of any work arounds?
Exact alert message:
This project is associated with Microsoft Azure Tools - v2.6 which is not supported in Visual Studio 2015. You must upgrade the project to target Microsoft Azure Tools -v2.7.
Download Microsoft Azure Tools -v2.7(already done)
Convert the project to target Microsoft Azure Tools -v2.7 (I can't, it is in production, and i don't have rights to do so)
Try this - If you still have access to VS 2013, install the 2.7 SDK for 2013, upgrade the project in 2013 and then try opening in 2015 w/ 2.7.
Has anyone recently tried to download Azure SDK for Visual Studio 2010? Going to the Azure site doesn't give the option any more; it only allows downloading SDK for VS2012 and VS2013.
Is VS2010 no longer supported?
Use the Web Platform Installer and search for "azure 2010".
The Azure 2.1 SDK is available for Visual Studio 2010 (with SP1).
Windows Azure SDK and Windows Azure Tools for Microsoft Visual Studio (March 2011)
http://www.microsoft.com/en-us/download/details.aspx?id=15658
it should not give you any problems.
If you're trying to download the latest SDK (version 2.2), it is not supported for VS 2010. See this blog post from Scott Guthrie: http://weblogs.asp.net/scottgu/archive/2013/10/22/windows-azure-announcing-release-of-windows-azure-sdk-2-2-with-lots-of-goodies.aspx. You should be able to download/install earlier versions of SDK using Web Platform Installer.
Unfortunately, this is not working with Visual Studio 2010 Ultimate. The web platform installer is responding with a list of errors.
I have installed the CRM 2011 SDK addin for visual studio 2012 (ultimate) and am trying to create a XAML Workflow Activity
I have added the CRM Workflow items to the toolbox using these instructions Add Microsoft Dynamics CRM Workflow Activities to the Toolbox
When I try and drop a Workflow on the design surface it say in red text "Could not generate view for Workflow"
Hovering over the text reveals a System.IOException that says "Cannot locate resource workflowdesigner.xaml"
How do I fix this?
You probably need to refer to the assemblies from VS. It's a bit of pain but a healthy conduct. In VS12 it's made a bit easier (finally, after a decade) to copy references from another project and (really, really finally) to refer to several DLLs at the same time.
It's the best practice and prefer conduct. :)
I fixed this by dumping the contents of my CRM SDK bin directory (about 24 assemblies) into C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PublicAssemblies
Not elegant but obviously there was a dependency in there somewhere.
Ondra is correct, this is a problem with the latest version of the SDK. Version 5.0.9690.3448 of the microsoft.xrm.sdk.workflow.dll does not work, whereas version 5.0.9688.1533 does not present the issue.
I had this issue occur on a XAML workflow that I previously had no problems with, and the issue turned out to be the upgrade of the SDK file.
Visual Studio 2012 Update 2 does not have any effect on this issue.
This example (and whole CRM workflow) under VS works properly only with CRM SDK version 1.0 - latest version 1.1 and version for VS 2012 causes described problem.
OK, I also hit this problem and made it work with your hints, I reached this result:
Changing VisualStudio version had no effect.
Changing the SDK version actually worked!
I am using SDK for CRM 2015 with version of 7.0.0.43 with visual studio 2015 and 2017. You can download it directly or use Nuget For "Microsoft.CrmSdk.Workflow" and "Microsoft.CrmSdk.CoreAssemblies"
SDK for 2018 (8.0.0) and Dynamics 365 (8.2.0.49) did not work.
Also Visual Studio 2012 Update 2 fix this problem
I would like to make a template for F# lib + XNA 4.0 + Xbox360 for visual studio 2012.
All I have is Visual Studio 2012 Express Edition for Web.
When I try to install the Visual Studio 2012 SDK, it stops after reporting that it requires Visual Studio 2012. The log seems to indicate it's looking for the Professional edition.
I'm not interested in buying a professional license for hobby work, and I am a bit surprised Microsoft would want to prevent hobbyists from extending their product.
I do have a professional license for Visual Studio 2010, though. If there's a way to make extensions for 2012 using 2010, that would work for me.
You can use VS2010 to develop extension compatible with VS2012.
All you have to do is to manually change vsixmanifest to make it work with newer version:
<SupportedProducts>
<VisualStudio Version="11.0">
Note however that Visual Studio Express does not support extensions, so you won't be able to install it in VS2012 Express anyway.