Skip to main content

Running Microsoft Playwright in an Azure Function using C#

When you have tried to run MS Playwright using C# in the context of an Azure Function, you probably have run into this message:


The driver it is referring to resides in the .playwright folder that is copied to the build output folder. Now, the output folder structure of an Azure Function project is different from most projects in the sense that there is an extra nested bin folder where the drivers should actually be copied. 

The build target that the Playwright team uses, at the time of writing (version 1.15.4), always copies the folder containing the driver to the root of the output folder. So the fix here is to add an extra build target to your project file, the corrects for the extra nested folder:

  <Target Name="FixPlaywrightCopyAfterBuild" AfterTargets="Build">
    <ItemGroup>
      <_BuildCopyItems Include="$(OutDir).playwright\**" />
    </ItemGroup>
    <Message Text="[Fix] Copying files to the nested bin folder of the azure function... $(OutDir)bin" Importance="high"/>
    <Copy SourceFiles="@(_BuildCopyItems)" DestinationFiles="@(_BuildCopyItems->'$(OutDir)bin\.playwright\%(RecursiveDir)%(Filename)%(Extension)')"/>
  </Target>

This will enable you to run the function. But this only works for the build scenario. When publishing the function to Azure, for instance, the output folder is different again. So we have to correct for that to:

  <Target Name="FixPlaywrightCopyAfterPublish" AfterTargets="Publish">
    <ItemGroup>
      <_BuildCopyItems Include="$(PublishDir).playwright\**" />
    </ItemGroup>
    <Message Text="[Fix] Copying files to the nested bin folder of the azure function for publishing... $(PublishDir)bin" Importance="high"/>
    <Copy SourceFiles="@(_BuildCopyItems)" DestinationFiles="@(_BuildCopyItems->'$(PublishDir)bin\.playwright\%(RecursiveDir)%(Filename)%(Extension)')"/>
  </Target>

Hope it will help people since I noticed more people encountering this issue.


Labels:

Comments

Post a Comment

Popular posts from this blog

Model View Update (MVU) pattern using ASP .NET components and Blazor

A primer on Model View Update (MVU) (UPDATE: The MVU library will be available via  Blazique/Blazique (github.com)  soon. The projects will be removed from Radix with the next major release after the move has been completed). The Model-View-Update (MVU) architecture is a sophisticated blueprint for designing interactive programs, including web applications and games. This architecture is characterized by a unidirectional data flow and is composed of three integral components: the Model, the View, and the Update. The Model is the heart of your application, encapsulating its state. The model preferably should be represented by an immutable data type. The View function is tasked with creating the visual representation of your application. It is a pure function that takes the current model as input and returns a user interface description, such as HTML elements or graphics. The View function refrains from performing any side effects...
Post a Comment
Read more

Blazique demo implementation of Conduit, from RealWorld

In the previous post, I announced Blazique, the MVU library for Blazor. An implementation of Conduit, the "mother of all demo applications", is in the works, and pretty far along at  Blazique/Conduit: RealWorld sample app Conduit implementation using Blazique (github.com)  ...  Conduit is an initiative from RealWorld to provide an exemplary real-world application to show the capabilities of libraries and frameworks. At the time of writing, more than 150 implementations are using a multitude of (combinations of) backend and frontend technology stacks. Check it out on  Welcome on RealWorld | RealWorld (main--realworld-docs.netlify.app)  and  gothinkster/realworld: "The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more (github.com) .
Post a Comment
Read more