Deploying to Linux in SaaS (Configured) Commerce

Deploying to Linux in SaaS (Configured) Commerce

With Optimizely SaaS (Configured) Commere now suporting net8.0 extensions dll, you will need to make a small tweak to how you distribute you extensions dll.

When looking in the documentation it is never mentioned but you need to add to a new netcore folder in the dist folder. Here is a snippet from my pipeline which builds the extensions dll and puts in in the right folder for Optimizely

- task: DotNetCoreCLI@2
  displayName: 'Build Code'
  inputs:
    command: build
    projects: 'src/Extensions/Extensions.csproj'
    arguments: '--configuration $(BuildConfiguration) --framework $(coreFramework) -p:Version=$(versionNumber)'

- task: CopyFiles@2
  displayName: 'Copy extensions dll'
  inputs:
    SourceFolder: './src/Extensions/bin/net8.0'
    Contents: 'Extensions.dll'
    TargetFolder: 'dist/netcore'
    OverWrite: true
Share :

I am senior solution architect working at Perficient helping brands create exceptional digital experiences for their customers. I am a full stack developer who enjoys the full software development lifecycle. I have expertise in Optimizely, the Azure cloud stack, React, NextJS, CI/CD pipelines, test driven development and solution architecture.

Related Posts

Using Azure Devops Pipelines in Optimizely SaaS (Configured) Commerce

Using Azure Devops Pipelines in Optimizely SaaS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployments. Any time a push is comitted to the configured branches the build service will start a deployment.

Read More
Net8 Local Development Without Docker In Saas (Configured) Commerce

Net8 Local Development Without Docker In Saas (Configured) Commerce

Introduction Now that Optimizely SaaS (Configured) Commerce has released net 8 support and updated their infrastructure to run on linux, we are starting to move some of our clients to .net 8 and linux hosting. This means we will need to be able to run .net 8 version locally, which according to offical docs requires docker desktop. While I love docker for creating images for deployed services, I hate using it locally because it consumes alot of diskspace, memory, as well as docker desktop no longer being free. This post will guide you on you can run locally .net 8 without using docker.

Read More