# Deploy Virto Commerce Platform on-premises or local environment

**URL:** <https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63>\
**Category:** installation\
**Tags:** video\
**Created:** [October 25, 2019, 6:21am UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63 "2019-10-25T06:21:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![OlegoO](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/olegoo/32/27_2.png) [@OlegoO](https://www.virtocommerce.org/u/OlegoO)\
**Post date:** [October 25, 2019, 6:21am UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/1 "2019-10-25T06:21:41Z")

</div>

Step by step instruction on how to deploy Virto Commerce Platform to on-premises IIS.

[![](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/1/18de2fbad3514f6321d41720fe7d11871df03f07.jpeg "On-premises Part 1. Deploy Virto Commerce Platform to on-premises (intro)") ](https://www.youtube.com/watch?v=YwX3kZSs-cU)

After setting up the Platform, you’ll be ready to deploy Storefront: to IIS or using .NET Core CLI.

> **[Deploy Virto Commerce Storefront to on-premises .NET Core CLI](https://www.virtocommerce.org/t/deploy-virto-commerce-storefront-to-on-premises-net-core-cli/68)**
>
> Step by step instruction on how to deploy Virto Commerce Storefront to on-premises environment using .NET Core CLI. Be sure to have Virto Commerce Platform accessible and running before watching this.

> **[Deploy Virto Commerce Storefront to Azure](https://www.virtocommerce.org/t/deploy-virto-commerce-storefront-to-azure/66)**
>
> Step by step instruction on how to deploy Virto Commerce Storefront from GitHub to Microsoft Azure. Be sure to have Virto Commerce Platform accessible and running before watching this.

---

<div class="post-metadata">

**Author:** ![barss](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/barss/32/1678_2.png) [@barss](https://www.virtocommerce.org/u/barss)\
**Post date:** [January 27, 2020, 12:33pm UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/2 "2020-01-27T12:33:33Z")

</div>

Hello, I’m trying to deploy vc-platform from source (v3.0.0) to express IIS & SQLLocalDB (VS 2019). There is an issue in start platform:

> ```
> **VirtoCommerce.Notifications** 3.0.0
> System.IO.FileNotFoundException: Could not load file or assembly 'Scriban, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null'. Не удается найти указанный файл. File name: 'Scriban, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null' at VirtoCommerce.NotificationsModule.Web.Module.Initialize(IServiceCollection serviceCollection) at VirtoCommerce.Platform.Modules.ModuleInitializer.Initialize(ModuleInfo moduleInfo) in C:\Projects\...\vc-platform\src\VirtoCommerce.Platform.Modules\ModuleInitializer.cs:line 46
> 
> ```

I deploy modules from source too. Tests of VirtoCommerce.Notifications fail. I tried to deploy VirtoCommerce.Notifications from binaries and had the same issue. Without VirtoCommerce.Notifications I enter the admin panel without error messages.  
What could be wrong?  
Thanks.

---

<div class="post-metadata">

**Author:** ![tatarincev](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/tatarincev/32/161_2.png) [@tatarincev](https://www.virtocommerce.org/u/tatarincev)\
**Post date:** [January 28, 2020, 8:09am UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/3 "2020-01-28T08:09:53Z")

</div>

Yesterday we released the new [RC3](https://github.com/VirtoCommerce/vc-platform/releases/tag/3.0.0-rc.3) platform version. Try to repeat deployment on this version and let us know if the error still exists.

---

<div class="post-metadata">

**Author:** ![barss](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/barss/32/1678_2.png) [@barss](https://www.virtocommerce.org/u/barss)\
**Post date:** [January 29, 2020, 4:06pm UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/4 "2020-01-29T16:06:48Z")

</div>

I tried to deploy rc3 from source, but there were errors with GitVersion. As far as I understand, rc3 from zip has no git history and this creates a problem for compilation. I could not solve this problem.

---

<div class="post-metadata">

**Author:** ![akak1977](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/akak1977/32/239_2.png) [@akak1977](https://www.virtocommerce.org/u/akak1977)\
**Post date:** [January 31, 2020, 5:10pm UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/5 "2020-01-31T17:10:58Z")

</div>

Could you explain more details, what are you doing? What is the goal? Do you want to run platform in some specific case? Could you describe this?

---

<div class="post-metadata">

**Author:** ![barss](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/barss/32/1678_2.png) [@barss](https://www.virtocommerce.org/u/barss)\
**Post date:** [February 2, 2020, 11:59am UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/6 "2020-02-02T11:59:19Z")

</div>

I managed to deploy v3.0.0 from source. The problem was in wrong version Scriban.dll in …/App\_Data/Modules. There aren’t this dll when deploy modules from source but it is installed when modules installed by admin panel. And I had there v2.0.0, which was caught while platform starting when v2.1.0 was needed.

---

<div class="post-metadata">

**Author:** ![akak1977](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/akak1977/32/239_2.png) [@akak1977](https://www.virtocommerce.org/u/akak1977)\
**Post date:** [February 3, 2020, 6:10am UTC](https://www.virtocommerce.org/t/deploy-virto-commerce-platform-on-premises-or-local-environment/63/7 "2020-02-03T06:10:35Z")

</div>

OK! Thank you! We will check it carefully before next RC.
