Is there a tool, or way to update your VisualStudio reference versions when a new version of the Azure SDK is installed?
Things like Microsoft.WindowsAzure.Diagnostics.dll and Microsoft.WindowsAzure.ServiceRuntime.dll are referenced by the folder
C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.8\ref\Microsoft.WindowsAzure.ServiceRuntime.dll
rather than a nuget package (which would be auto updated when the nuget reference is updated). I noticed after cloning a repo to a machine with only v2.9 installed that my solution wouldn't build as there was a hard dependancy to an SDK version.
Related
So I have downloaded the latest SlowCheetah Visual Studio Extension v2.5.48.45331 and installed the latest NuGet Package. I have a custom build configuration named XL.Production and have the according Web.XL.Production.config file. When I publish, Web.XL.Production.config is picked up and everything's sugar, but when I hit F5, no go, Web.config settings are used even though XL.Production configuration is currently selected.
I have checked out this question: SlowCheetah not transforming file on build
But the latest SlowCheetah is not using PropertyGroup any longer and instead relies on the NuGet Package.
So it's not working for me, it was clean install, we never had any previous version of SlowCheetah installed. We are using VS2013 w/Update 5.
p.s. Just a thought, why is such a critical functionality not built in into VS by default? Why should I have to install a NuGet package and a Visual Studio Extension to get this to work?
Project references to the various parts of the Azure SDK should live in the installation of the Azure SDK, but for some odd reason my code (an Azure Mobile Service) can no longer see Microsoft.WindowsAzure.Diagnostics:
I should be able to pick the Microsoft.WindowsAzure.Diagnostics.dll up from my Azure SDK 2.7 installation, but here's what I see in the SDK's 'ref' directory:
I.e. I just have
Microsoft.WindowsAzure.ServiceRuntime.dll
WindowsAzureEventSource.dll
WindowsAzureTelemetryEvents.dll
but I do not have Microsoft.WindowsAzure.Diagnostics.dll. Interestingly there is an NuGet package called Unofficial.Microsoft.WindowsAzure.Diagnostics, with over 30,000 downloads, which suggests that I am not the only one having this problem.
Where should I reference Microsoft.WindowsAzure.Diagnostics from; is it a DLL somewhere in an SDK or in a NuGet package; where is it?
You can find it here: C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.7\bin\plugins\Diagnostics. With SDK version 2.5, diagnostics is now a plugin.
It's not in C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.7\ref, but is in
C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.7\bin\plugins\Diagnostics\Microsoft.WindowsAzure.Diagnostics.dll
It was a simple matter of removing the stale reference and re-adding it through the Reference Manager:
Can someone help me figure out where CloudConfigurationManager exists in Azure SDK v2.4?
CloudConfigurationManager, in the v2.3 SDK, is located in:
C:\Program Files\Microsoft SDKs\Windows Azure.NET SDK\v2.3\ref\Microsoft.WindowsAzure.Configuration.dll
The 2.4 SDK is at C:\Program Files\Microsoft SDKs\Azure.NET SDK\v2.4
And there's no such Microsoft.WindowsAzure.Configuration.dll in that directory..
MSDN still shows CloudConfigurationManager in Microsoft.WindowsAzure.Configuration.dl: http://msdn.microsoft.com/en-us/library/azure/microsoft.windowsazure.cloudconfigurationmanager.aspx
And so the only way I can get my project to compile is if I have both the 2.3 and 2.4 SDK installed at the moment.
I found it in Microsoft.Azure as opposed to Microsoft.WindowsAzure
It is in the folder C:\Program Files\Microsoft SDKs\Azure.NET SDK\v2.4\packages as a local NuGet package (see below). Also, there is a file in that directory titled LocalPackagesInstallationInstructions.docx that explains how to add it as a path for your NuGet Packages. If you have a new dev environment installation (as I did recently) then you may find this helpful.
Latest Answer .
Install Package Microsoft.WindowsAzure.ConfigurationManager.3.2.1 or newer
which contains Microsoft.Azure namespaces which is having this class. CloudConfigurationManager
1.Download Cloud Configuration NuGet package
https://www.nuget.org/packages/Microsoft.WindowsAzure.ConfigurationManager/
2.Install the package from local by solution NuGet package Manager
3.In code you will find class in Microsoft.Azure.CloudConfigurationManager
It's a provider hosted project. It used to work until very recently.
If I create a completely new project/solution, then it works.
If I start the old one, or redownload it from source control, I get the following error:
NuGet Package restore failed for project LocalTheaterWeb: Unable to find version '3.0.1' of package 'AppForSharePoint16WebToolkit'
I tried Update-Package -Reinstall but the problem stays.
Any ideas?
The solution of Scott Hillier did it for me:
http://www.shillier.com/archive/2014/08/05/nuget-package-restore-fails-for-sharepoint-2013-provider-hosted-apps.aspx
I often take advantage of the NuGet Package Restore capability to
reduce the size of my projects when saving or sharing them. Today, I
discovered an issue with this process when building SharePoint 2013
Provider-Hosted Apps against SharePoint Online. Here are the steps to
reproduce and the fix:
Create a Provider-Hosted App in Visual Studio 2013 using a SharePoint Online site for debugging.
Right click solution and "Enable NuGet Package Restore"
Save and Close Project
Delete the “packages” folder from project directory
Open Project in Visual Studio 2013
Rebuild, receive error “Unable to find AppForSharePoint16WebToolkit”
Open Packages.config file
Change “AppForSharePoint16WebToolkit” to “AppForSharePointWebToolkit”
Rebuild – successfully this time. Apparently, the "AppForSharePoint16WebToolkit" package is not available through the
NuGet Package Manager, but the older "AppForSharePointWebToolkit"
package is available.
The error message suggests that NuGet cannot find the AppForSharePoint16WebToolkit package in your package sources. So check the following:
The correct package source is selected whilst doing the Update-Package -Reinstall.
Check the package source that hosts the NuGet package is enabled. If you are using a recent version of NuGet the package restore should use all the enabled package sources.
See if the solution or project has its own NuGet.config which is overriding the package sources.
Without further information my guess is 3. since you say it works for a new project.
You can also run Fiddler to see what package sources NuGet is using as it tries to restore.
For older "locked down" projects with specific package version numbers that you can't update, un-check "Automatically check for missing packages during build in Visual Studio" which is found via:
Nuget Package Manager > Package Manager Settings
This means that if you toggle between newer projects and older projects you need to check and un-check this setting
Using Visual Studio 2012 Premium on Win 7 x64, I make a new project (an MVC 4 project). When right-clicking on the project, I see no 'Manage NuGet Packages' option. A packages folder exists in the solution directory, as does a package.config file in the project directory. When going to Tools, there is no Manage NuGet Packages option, either. When going to Tools->Extensions and Updates..., the NuGet Package Manager is installed and up to date.
Any idea why my project is unable to manage the NuGet packages for itself?
Here's a screenshot of the menu:
I had a similar problem. The problem was next:
I've installed NuGet Packager instead of NuGet Package Manager (from Extensions and Updates). Once I've installed the last one, it appeared in the context menu. Maybe you faced the same problem.
I had to uninstall the Nuget Package Manager from Extensions and Updates, and then reinstall it. After restarting Visual Studio, the missing menu entries appeared.
My solution came in the form of wiping out all traces of the NuGet Package Manager, including all registry files. Because the registry files have weird names, searching for things like NuGet.Core as well as just about anything in the Program Files\Microsoft Visual Studio\11.0\Common7\IDE\Extensions folder. After clearing those out, restarting the computer, reinstalling NuGet, and then restarting again seemed to clear up the issue.
First of all there are something's you should check
Make sure you are in debug mode
Make sure your not running the debugger
The 'NuGet Package Manager' is installed and not the 'NuGet
Packager'
Your project was created using the VS IDE - to check this, you can
simply create a new solution in VS and see that you are still
missing the 'Manage NuGet Packages' option in the menu.
Now if this issue still appears you can try taking the following steps:
Clean out your Extensions folder.
Extensions folder can be found
under the VS folder \Common7\IDE\Extensions. i.e. if vs2013 in 64
bit, then C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\IDE\Extensions
Uninstall the NuGet Package Manager from Extensions and Updates
Restart VS
Install the NuGet Package Manager from Extensions and Updates
Hope this was helpful
Because of reasons, It seems that Nuget Package Manager was not installed on my fresh Visual Studio Professionnal 2013 edition.
Installing it fixed the problem.
You can also check your Extensions folder in [if vs2013 in 64 bit, then C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions]
Each extension has folder in here with manifest file extension.manifest, check these xml files - node "Name" and if found duplicate, remove duplicate folders, restart Visual Studio.
If there is same extension in different folder, VS is confused and will not load it...
In my case the project was running. When stopped, the menu items appeared.