I'm trying to debug an Azure Function, but there doesn't appear to be a way of changing the Debug/Release mode from within the new Azure Functions tools in Visual Studio 2017.3.
How do I debug?
As far as I know, the vs2017 preview doesn't provide the way to directly change the publish setting.
I suggest you could find the publish profile and change its setting by yourself.
More details, you could follow below image:
1.Open the application folder
2.You could locate the profile file folder and find the publish profile.
\Properties\PublishProfiles
3.Open the profile and change the release to debug.
The result is like this:
Notice: To see the configuration changed, you need reopen the visual studio preview.
Related
I am trying to create a new Azure Resource Group Project for Creating a Logic Apps Solution in Visual Studio 2015 however I am facing the below error mentioned in the Screenshot.
It seems a issue caused by visual studio instead of azure. You may have a corrupt install and depending on the order that dlls are loaded determines whether you see the error or not.
This is a workaround in the similar issue that you could refer to.
The workaround - which does not always work right away - is to Sign out of Visual Studio (This takes 2 attempts to sign out and remove the credentials). Then reboot the PC. Once logged into WIndows, launch Visual Studio - DO NOT SIGN IN. Open the solution, right click on the Deployment project; which may or may not trigger the same dialog error. If the deployment dialog is display, then i can add account and deploy. Otherwise, i must turn off the PC and try again, and again, and again, until it starts working.
I recommend you can try the workaround if necessary.Then you could report the problem and ask the Microsoft visual studio support for help.
screen shot of the argument of publish task
screen shot of the publish to path in artifact
and plz dont give me reference of this link Visual Studio Team Services Release/Deploy fails - "No package found with specified pattern" because it didnt work for me..!!
The default .NET Core publish build task looks for web.config or wwwroot to identify a target for a web app.
To fix this:
uncheck the "Publish Web Projects" checkbox
In the “Projects” edit box enter */*.csproj
This will let the build publish the right artifacts in the drop folder for the release run to pick them up.
I am currently developing an Azure Logic App. This is very straight-forward from portal, but I need to use Visual Studio as an IDE for this. I have followed all the steps mentioned in https://azure.microsoft.com/en-in/documentation/articles/app-service-logic-deploy-from-vs/ article, but when I try to do right-click "<>.json" and say "Open in Logic App Designer", the Visual Studio crashes everytime.
Could anyone please assist on the same?
Thanks
I has a similar issue, I found I had to install the Azure Logic Apps Tools (https://marketplace.visualstudio.com/items?itemName=VinaySinghMSFT.AzureLogicAppsToolsforVisualStudio), restart Visual Studio and then create the Azure Resource Group project for it to work.
The project that I had generated without the tool installed did not work (ever).
I'm using the Azure SDK 2.9.6, Visual Studio 2015 update 3
Are you currently signed into Visual Studio with an account containing valid Azure subscriptions/currently has strong internet connectivity? That is known to cause editing issues before.
If that does not solve your problem, we have enabled logging feature in our most recent update (ver 1.0.0):
a. Open developer command prompt for VS2015
b. Run following command to start VS with activity logging enabled.
devenv.exe /log
c. Repro the issue in this instance and close it.
d. You can find the activity log at location :
%APPDATA%\Microsoft\VisualStudio\14.0\ActivityLog.xml
e. Please send us this file to us.
If you can share the logs with logicappsbug#microsoft.com, we can further assist you on this specific problem.
Thanks,
Max
I would like to be able to publish an application and have it so that someone could navigate to a website and download a setup executable. Then when they run that executable it would download and install all the associated applications that work with my application.
Is it possible to have visual studio publish it to do this?
Or do I have to program an custom setup application.
It seems that there are options for this in the publish section of the project properties.
But I can't seem to find out exactly what everything does.
There is an updates button in the publish tab that I would like someone to explain how that works as well.
It looks like ClickOnce will work for you.
ClickOnce is a Microsoft technology that enables the user to install
and run a Windows-based smart client application by clicking a link in
a web page.
http://msdn.microsoft.com/en-us/library/31kztyey.aspx
You can try Windows Installer XML (WiX) Toolset
http://wixtoolset.org/documentation/manual/v3/votive/authoring_first_votive_project.html
Our team has been having quite a lot of trouble with Visual Studio's publish feature. We use TFS and are all running VS 2012 ultimate. It works fine when only one person is involved in a project, but when we get many people inside one project, the publish profiles get off and Visual Studio reports a successful publish even when all files haven't been copied up. I've read all the SO questions about why this happens and I understand that TFS adds the publish profiles to the source control automatically. If we create a new publish profile and republish, everything works. But this is not sustainable. I can't prevent VS from automatically adding the publish profiles to TFS (if we could, I think this would solve the problem) so I'm now looking for better ways to publish an application to a web server. Is there a better tool out there to publish web applications or do I need to write my own VS extension?
Per this question (https://stackoverflow.com/a/12393154)
The temporary answer seems to be to change your settings from release to debug, save, then switch it back. This causes the pubxml.user file to be rebuilt, which is actually the problem.