Azure Remote debugging vs2015 support - azure-web-app-service

I've tried to set up the remote debugger for Azure Websites, Azure websites only seem to support remote debugging on VS2013 or VS2012, not 2015.
Is there a way to work around this issue?

Please make sure you have the latest VS2015 and SDK and try it from time to time. The plan is obviously to support VS2015 too, but please keep in mind that until there is the release version of VS, things might get broken from time to time. Basically there has to be a client version and server version of this aligned and in the preview versions it might happen that they are not backwards compatible and they get out of sync.
Unfortunately, there is not much you can do about it at this moment. If you need this for your business, I would recommend to use VS2013, which you can have installed side by side along with VS2015 Preview.
Hope this helps.

Related

Running Azure functions will result in .net 4.7.1 installation prompt dialog

When I try to run (debug) functions in Visual Studio 2017 on one of our machines, the following dialog pops up!
The target framework for the project is <TargetFramework>net461</TargetFramework>. For some reasons I am not able to install .NET 4.7.1 and now I am completely lost. I am sure it was functioning in the past on the same machine. Probably one of the updates caused it.
Any idea how to resolve it?
This is because the latest version of the Azure Functions Tools for Visual Studio now requires .NET Framework 4.7.1 (as of February 2018).
Note that this does not impact the target framework that you compile against - only the target framework your code runs against. Similarly, when you run in Azure, you can expect the .NET runtime version to be .NET Framework 4.7.1 (at the time of writing).
I tried implementing the solution mentioned in comment. However, it didn't work for me. However, reverting the Azure Functions Tools to previous version worked. Thanks Chris for pointing that it was Azure Tools and not any packages that caused it.
If anyone else should come across this.
For me, the issue was the actual func.exe config that needed to be upgraded.
Navigate to:
C:\Users[USER]\AppData\Local\AzureFunctionsTools\Releases[VERSION]\cli
.. my version was 1.4.0
Modify the func.exe.config to match the .net version installed
.. it was 4.7.1

Unable to connect to IIS express, using DNX beta5

After I updated VS2015 yesterday and I cannot run my project (singla page app) anymore... Visual Studio says: Unable to connect to IIS express
I am using Solution DNX SDK version: 1.0.0-beta5
And my project.json is:
My references:
So everything should be ok ??
What am I doing wrong ?
BR
You have to understand that direct IIS hosting is no longer supported (and probably never will be again)! This is a decision by the ASP.Net team at Microsoft to completely concentrate on the kestrel server which is anyway required for Mac/Linux/Docker. By concentrating on one server the quality rises for everyone. Like Node, Kestrel recommends to use a reverse proxy in front of it. For that you can use your IIS/nginx/Apache.
I would urgently recommend you setup your project with RC1 and change to kestrel with HTTPPlatformHandler (in VS2015 Update 1 that works transparently with IIS Express for you). Beta5 is very outdated for many things.
It might be possible that your project could take a few hours before being able to run again.
First, you skipped beta6, beta7, beta8 and we are now at RC1.
Check which runtime you can use in Visual Studio and make sure you run with the latest one.
Once this is done, ensure that all your dependencies branded beta5 are renamed to the proper version that is in your Visual Studio. Some packages may have been removed, classes moved and many other things.
Check here for breaking changes:
Changes in beta6
Changes in beta7
Changes in beta8
Changes in rc1

VS2008 Azure storage client compatibility issue

According to this article some support for older versions of Azure are going away:
https://azure.microsoft.com/en-us/blog/microsoft-azure-storage-service-version-removal/
We have a vs2008 application that is uploading files to Azure. {Using Azure 1.2 (for VS2008) - Microsoft.WindowsAzure.StorageClient v1.0.0 - Runtime v2.0.50727}.
We can't have this break since we are using this in production.
I need to know if there is a clear way to know if this is going to stop working.
I would really like to know if there is a way to upgrade the vs2008 project to use a compatible version of the StorageClient without migrating the project to vs2015.
Your version of the library should still be supported after the service removal. You can confirm which version of the service you are hitting by running requests through Fiddler and checking the x-ms-version. As you can see in the most recent post regarding our service deprecation, we are only removing version 2009-07-17 and older as of August 1, 2016.

Getting Error on Publish the Azure Application

When i am trying to make package of cloud application code my visual studio is getting restart.I am unable to make a package,please suggest me solution ASAP.
If you mean Visual Studio crashes when you build a Windows Azure application, please try to reinstall the Windows Azure tools. Moreover, you can also use CSPack to manually create the package. I would like to suggest you to check http://msdn.microsoft.com/en-us/library/gg432988.aspx for more information.
In addition, if the issue is still encountered, please provide more information as other communities point out, then we can find the issue more conveniently and provide further suggestions for you.
Best Regards,
Ming Xu.

User Experiences for Visual Studio 2008 extensions for SharePoint v1.3 CTP

In January, MS released a CTP of VS Extensions for SharePoint v1.3. Has anyone used these? What have your experiences been?
We used the previous version and did not like how much was hidden/abstracted from the developers. We eventually abandoned the extensions and create our own WSP's with MakeCab.exe.
...Peter
The install of the website that runs the webservices completely failed and I could never get it to work so I uninstalled it.
Till today I didn't encounter any problems with VSeWSS 1.3. except some issues with the VSeWSS's web service, which were related to a name resolving problem of my PC.

Resources