I know that this is not an appropriate question for here.
But I've looked everywhere, and cannot find an appropriate solution.
What im trying to do is install CRM 2015 SDK on to Visual Studio 2013, to develop plugins, web resources etc..
I know its a stupid question , but can you please help.
The SDK for CRM 2015 doesn't include the Developer Tools (unlike the previous versions). They're to be shipped at a later date (AFAIK they still haven't picked one).
Microsoft says you should be able to make do with the 2013 version, if you update the DLLs references from the 6.x to the new 7.x version ones. Also, you'll probably have to toy with the target framework (CRM 2015's plugins must target .NET 4.5.2).
I personally gave up on the Developer Tools a long time ago, and have gone back to building Class Libraries, since I have to tweak 2011, 2013 and 2015 environments, both on-premise and online ... and multiple Dev Tools setups don't "stack" nicely on the same VS installation.
Related
UPD: I found old article that I used a few years ago and followed me step-by-step with deploy using Windows Installer Deploying a VSTO Solution Using Windows Installer. Problem solved
I wrote a custom add-ins menu for Office using Visual Studio Community 2019. Now I'm trying to deploy it. In this article Deploy an Office solution by using Windows Installer they used VS2013 and InstallShield Limited Edition, which doesn't work with VS Community 2019. I installed Advanced Installer but in the Help section "Create a package to deploy an Office Add-In developed in Visual Studio" says "The following article uses options that are available starting with the Professional edition and project type." what means I need to upgrade free version to commercial.
Could you please recommend any other Windows Installer for Office solution for Visual Studio Community 2019? Or any step-by-step article how to deploy solution by using Setup Project in VS Community 2019?
I remember I tried to do some deploy in old version of VS a few years ago, but nowadays it seems more complicated. I just want to try and see if my add-ins work in another computer and then I'll think about commercial versions of VS or Installers
Thanks,
Elena
You can build the package using the free version of Advanced Installer too, but you will have to create all the registry entries (those related to your addin) manually and also the same for adding the files in the package, as documented in the MS article.
The wizard that you mention above does this automatically by reading the necessary info to make the configs from your Visual Studio solution.
Disclaimer: I work on the team building Advanced Installer.
I have a Microsoft Visual Studio solution that I have been using for many years for producing a new release of our software application. One of the projects has recently stopped loading.
It looks like the problem may be similar to:
Visual Studio 2013/2015 Can't Load Azure Project
However in that case it was a new installation of Visual Studio.
Looking in add/remove programs it appears that 'Microsoft Azure Tools for Microsoft Visual Studio 2013' has an installed date of 19th May this year and version number 2.5.21104.1601.
What is the simplest way for me to fix this problem? Should I uninstall the Azure Tools and see if I can download and install V2.4? or do I need to install a new version of Azure SDK, as the other question suggests?
Another option I have, might be to upgrade to Visual Studio 2017. I have been reluctant to do this, as am not sure what things might break.
EDIT: I notice in Extensions and Updates there is Microsoft Azure SDK 2.9 available. Should I install this?
Any suggestions appreciated.
Thanks
Phil.
As you said you could try installing Microsoft Azure SDK 2.9.
Here is the Microsoft Release summary for Azure SDK 2.9.
Before installing Azure SDK 2.9 you should read this document whether your project having all the support in this SDK. If not then you should upgrade to, VS 2017.
From a developer word, I'd say upgrade to VS 2017 where you get/support all the latest features in your hand.
This seems like a weird problem. I've just upgraded to a brand new PC and I can't for the life of me work out where I can get visual studios 2010 from. I have my product key ready to go.
Has MS discontinued this product? If so is there a work around? Is my only option to (dare I say it) upgrade.
According to Microsoft there's no more Visual Studio 2010 for download from their (official) site.
Personally I really recommend you go straight to 2017 Community Edition - it has everything the 2010 Professional has and more.
The "more" includes built-in support for GitHub, "almost" full support for C++11 and some support for C++14, Windows 10 SDK, parallel builds, built-in support for Linux remote build/debugging... The list goes on and on.
For past express editions, I've been able to find a "compare editions" page that shows what features are available in express, professional, ultimate, etc. Something like this.
However, every comparison table I've seen so far omits the express editions. Surely Microsoft must have a list of things you get by upgrading to Visual Studio Professional from an Express Edition--after all, it's a free product, and they would like you to upgrade to a paid product! So, where have they hidden this feature comparison table, or "reasons to upgrade to Professional" list?
As far as I know there is no single table with a summary.
It depends on which version of express your talking about. Express is split up into a lot of different SKUs based on the type of product you're building; Web, Phone etc. Which is probably why there isn't an entry on this table for Express. 2013 was a point release to 2012 and there is a comparison of Express Web 2012 to Pro on MSDN.
The biggest single difference is that you cannot run plugins in Express. This means no Resharper, Test Driven .NET etc. This also applies to some plugins that you might consider to be written my Microsoft because they were not part of the official Microsoft release, for example plugins written my various other groups. This is a long-standing gripe for users of Express and looks like it is still the case for 2013, How to install Nunit plugin in Visual Studio 2013 Express?.
I was very surprised when I downloaded Visual Studio 2013 Express Edition for web development on my new Windows 8.1 machine, and it was starkly different from what I believe is the identical product that I have been using for a while on a Windows 7 machine.
For example, when creating a very small demo app using Web API (from the asp.net website), the "New ASP.Net Project" wizard did not offer Web API. And the new project did not include the App_Start folder, which would include code for things like routing.
I tried to use NuGet to add the essential features, but no luck. That tutorial only took a few minutes on Windows 7, but was a miserable failure and an hour I will never get back on Windows 8. I don't really understand Microsoft's strategy here.
From what I observed Visual Studio Express 2013 doesn't come with a 64-bit compiler.
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC>vcvarsall.bat x64
The specified configuration type is missing. The tools for the
configuration might not be installed.
And since the Win 8 SDK doesn't provide compilers anymore either, it appears like you must pay for Visual Studio 2013 Pro or you won't be compiling 64-bit binaries.
"The Windows SDK no longer ships with a complete command-line build
environment"
https://dev.windows.com/en-us/downloads/windows-8-sdk
Actually in VS2010 professional edition, there was no code contracts. I had installed the standard version of code contracts.
Now in the Visual Studio 2010 > project properties > I get the code contracts tab.
My Question is if i have used the code contracts in my code, do i need to ship my project with any special dll or other thing so that the code contracts work after deployment.
Also, i am not currently planning to purchase the professional edition of code contracts. kindly explain me.
* Newly Added *
I would like to know whether using this mechanism will affect the use of Enterprise Library features like Unity & Exception logging. Also will this work for WCF, because if some new C#4.0 features are not supported in WCF.
I can't answer all of your questions but I can say that Code Contracts can be used in VS Professional edition but to get build-time checking to work in Visual Studio you will need VS Premium and up from what I understand.
Also if your interested I did put in a feature request to support Code Contracts in all editions of Visual Studio and I could use a little help adding some votes to it to get some attention from Microsoft.
Apparently they have the made the static checker available to all editions of Visual Studio in their 1.4.412128.0 release (December 28, 2011).
Check the release notes and you can download the latest msi here.
-Hope this helps