![How To Minimize Functions In Virtual Studio, For Mac How To Minimize Functions In Virtual Studio, For Mac](https://code.visualstudio.com/assets/docs/editor/accessibility/zoomed-in.png)
Now that VS 2015 is no longer offered except through legacy channels to MSDN subscribers, and VS 2017 has released several post-RTM updates, this has become more important. My team has to maintain installations of both 2015 and 2017 just for the Azure Functions support in 2015. Frankly, we are regretting the purchase of 2017 and the choice of Azure Functions. This disjointed support, combined with the lack of schedule communication feels like amateur hour. Absent any evidence to the contrary, there must be something wrong with the development effort to integrate into VS2017, or we would at least hear some rough dates. Instead: 'we have no dates to share'. You need to share something, because this is hurting both Azure Function and Visual Studio 2017 adoption.
In Visual Studio, if I have a code file open, I can press CTRL + M or CTRL + M + O to collapse all code blocks, regions, namespaces, etc. How to I do the opposite and expand everything? I have Googled this, but cannot seem to find a shortcut that works!
![Minimize Minimize](https://www.jimbobbennett.io/content/images/2017/08/ch14_add_new_uitest_project_mac.png)
I guess my first response to your question would be why? Why would you want to do something you would normally do in a windows app in an Azure Function.
Functions are sold as a good answer to a compute problem, where you only want to pay for the usage you actually use to compute, as a good cloud offering should. They should be parallel processors that are short lived but highly utilised whilst alive, so the idea of converting a Windows App, to something like that seems an unusual thing to do, which is probably why there aren't any good guides. If there is a piece of logic that kills your computer that you want to take out of the app into a Function, that would work well (Assuming you're set on using functions, personally after the last 2 months I'm going to walk away from them and see what's happening in 6 months). In which case follow the guide that Donna posted to create a web app and convert it. Then you can call your function via a queue for instance from your c# app, and poll a little app service of some sort to see when the job is complete. Just my thoughts, but atm, in the current state of tooling. Think carefully before proceeding with Functions.
Hi @dreadedde, I have a single Windows app that I am running now. In the future, I want all my apps (Windows, Mac, Web, etc.) to run much of the same business logic locked up in my current app. To do this, I am looking into creating APIs that run Azure Functions.
I do not want to re-write all my code, so it seems like a good idea to take my current classes and move them up into Functions (albeit with modifications). I am trying out the demonstration link Donna posted now to see how far that gets me. I completely understand your thoughts re:the tooling. I did a lot of research up to now to determine what the best approach is and this whole time I was under the incorrect assumption that Microsoft already had tooling figured out so will see what happens next. Thanks for your thoughts. Hi I am still going through the design and quite frankly am still learning, but here is what I thought would be the right thing to do:. Create APIs for the core functionality of my product.
Create Functions to handle the business logic on behalf of the API. Create a logic app that orchestrates the Functions and performs some of the transformations my code needs to perform. I know this thread is going slightly off topic from the original, but do you have thought son the matter? Happy to take the conversation offline.
I just went through the VSTS build, and it turns out you need to make some customizations form the default App Service Deploy template:. Use NuGet version 4.0. Change the msbuild arguments for the solution build step to the following: /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation='$(build.artifactstagingdirectory) output.zip' /p:DeployIisAppPath='Default Web Site' I'll do a blog post soon that walks through everything. Right there with you. I meant to ask this when I was at Build last week and it slipped my mind. I just did a quick first pass last night just to see if the story changed since it appears we have a new project type with 2017 that didn't require the workarounds of VS2015 azure function toolset.
Local instance dev works great, publishing manually works fine, but when I setup continuous delivery in Azure and it's not picking up on the functions. Was looking for some quick guidance before I started hacking around;) Thinking maybe this should be in its own issue as this thread is probably getting retired so let me know and I'm happy to move it to a new issue (or a more appropriate place for discussion):).