nopCommerce 4.00 BETA released. Please share your impressions

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
omerakar wrote:
Dear nopCommerce community!

The new version of nopCommerce is about to be released. But before we announce it officially, we want you to BETA test the upcoming nopCommerce 4.00 and share your feedback with us.

In this version, our development efforts were focused on moving nopCommerce to ASP.NET Core 2.0, performance and architecture improvements, further enhancements, and bug fixing. The highlights for this version:

•  Migration to ASP.NET Core 2.0. Please note that we target .NET Framework 4.6.1 and not .NET Core. We plan to use .NET Core only when EF Core team starts supporting all ORM functionality from the classic Entity Framework 6. Such as lazy loading, etc (they plan to do it in Q1-Q2 2018).
•  Significant performance enhancements. It’s not just about migration to ASP.NET Core. We’ve made many other changes to increase performance

The release notes don’t include all changes caused by migration to ASP.NET Core. Here is a separate upgrade guide for developers on how to migrate existing projects and plugins to this version because the number of changes is really HUGE! You can find the full release notes here.

In order to download nopCommerce 4.00 BETA please use the following links:
BETA 4.00 - Source code (download if you are a web developer interested in the nopCommerce application source code)
BETA 4.00 - No source code (download this package if you want to deploy a live site to a web server with the minimum required files)
Upgrade script from 3.90 (download this package to upgrade an existing installation to a newer version)

We'd love if developers could get involved with testing to find any issues which will need fixing before the final release. Please share your thought after testing in this forum topic. Please also learn more about our BETA testing program here (earn $10 for each reported bug). Thank you!

Hi Andre,
I am getting following errors;

1>------ Build started: Project: Nop.Core, Configuration: Debug Any CPU ------
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1964,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
1>Caching\MemoryCacheManager.cs(6,28,6,38): error CS0234: The type or namespace name 'Primitives' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?)
1>Infrastructure\IEngine.cs(4,28,4,41): error CS0234: The type or namespace name 'Configuration' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?)
1>Infrastructure\INopStartup.cs(2,28,2,41): error CS0234: The type or namespace name 'Configuration' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?)
1>Infrastructure\NopEngine.cs(10,28,10,35): error CS0234: The type or namespace name 'Hosting' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
1>Infrastructure\NopEngine.cs(12,28,12,41): error CS0234: The type or namespace name 'Configuration' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?)
1>WebHelper.cs(9,28,9,39): error CS0234: The type or namespace name 'StaticFiles' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
1>WebHelper.cs(10,28,10,38): error CS0234: The type or namespace name 'Primitives' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?)
1>Infrastructure\IEngine.cs(27,73,27,91): error CS0246: The type or namespace name 'IConfigurationRoot' could not be found (are you missing a using directive or an assembly reference?)
1>Infrastructure\INopStartup.cs(17,61,17,79): error CS0246: The type or namespace name 'IConfigurationRoot' could not be found (are you missing a using directive or an assembly reference?)
1>Infrastructure\NopEngine.cs(176,80,176,98): error CS0246: The type or namespace name 'IConfigurationRoot' could not be found (are you missing a using directive or an assembly reference?)
1>Done building project "Nop.Core.csproj" -- FAILED.
Package Microsoft.AspNetCore 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication.Cookies 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication.Cookies 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package AutoMapper.Extensions.Microsoft.DependencyInjection 3.0.1 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package AutoMapper.Extensions.Microsoft.DependencyInjection 3.0.1 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.DependencyInjection 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.DependencyInjection 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Configuration 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Configuration 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Diagnostics 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Diagnostics 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Primitives 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Primitives 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Http 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Http 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication.OAuth 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication.OAuth 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Mvc 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Mvc 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Session 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Session 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Hosting.Abstractions 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Hosting.Abstractions 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.DataProtection.Redis 0.3.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.DataProtection.Redis 0.3.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Caching.Memory 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Caching.Memory 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.StaticFiles 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.StaticFiles 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Routing 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Routing 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Configuration.Binder 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Configuration.Binder 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Http.Extensions 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Http.Extensions 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Options 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Options 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
One or more packages are incompatible with .NETFramework,Version=v4.6.1.
Package Microsoft.AspNetCore 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication.Cookies 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication.Cookies 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package AutoMapper.Extensions.Microsoft.DependencyInjection 3.0.1 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package AutoMapper.Extensions.Microsoft.DependencyInjection 3.0.1 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.DependencyInjection 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.DependencyInjection 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Configuration 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Configuration 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Diagnostics 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Diagnostics 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Primitives 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Primitives 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Http 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Http 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication.OAuth 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication.OAuth 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Mvc 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Mvc 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Session 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Session 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Hosting.Abstractions 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Hosting.Abstractions 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.DataProtection.Redis 0.3.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.DataProtection.Redis 0.3.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Caching.Memory 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Caching.Memory 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.StaticFiles 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.StaticFiles 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Routing 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Routing 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Configuration.Binder 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Configuration.Binder 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Http.Extensions 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Http.Extensions 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Options 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Options 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
One or more packages are incompatible with .NETFramework,Version=v4.6.1.
Package Microsoft.AspNetCore 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication.Cookies 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication.Cookies 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package AutoMapper.Extensions.Microsoft.DependencyInjection 3.0.1 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package AutoMapper.Extensions.Microsoft.DependencyInjection 3.0.1 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.DependencyInjection 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.DependencyInjection 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Configuration 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Configuration 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Diagnostics 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Diagnostics 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Primitives 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Primitives 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Http 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Http 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication.OAuth 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication.OAuth 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Mvc 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Mvc 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Authentication 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Authentication 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Session 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Session 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Hosting.Abstractions 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Hosting.Abstractions 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.DataProtection.Redis 0.3.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.DataProtection.Redis 0.3.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Caching.Memory 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Caching.Memory 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.StaticFiles 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.StaticFiles 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Routing 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Routing 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Configuration.Binder 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Configuration.Binder 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.AspNetCore.Http.Extensions 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.AspNetCore.Http.Extensions 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
Package Microsoft.Extensions.Options 2.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Microsoft.Extensions.Options 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0)
One or more packages are incompatible with .NETFramework,Version=v4.6.1.


I think because of VS 2017 version, mine is 15.2 It requires 15.4

https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#15.4

.NET Standard 2.0
6 years ago
Can you please list the dir that need permissions set.

I am getting the below error. I think it is due to permissions settings.

An error occurred while starting the application.
.NET Framework 4.7.2117.0 X86 v4.0.0.0    |   Microsoft.AspNetCore.Hosting version 2.0.0-rtm-26452    |    Microsoft Windows 6.3.9600    |   Need help?


Thanks you.
6 years ago
For this one, it is the IUSR write  permission for Plugins.   Also create a folder called bin under plugins.  This should fix this error, but you will need to assign more write permission for bunch of other folders


hitnet wrote:
Can you please list the dir that need permissions set.

I am getting the below error. I think it is due to permissions settings.

An error occurred while starting the application.
.NET Framework 4.7.2117.0 X86 v4.0.0.0    |   Microsoft.AspNetCore.Hosting version 2.0.0-rtm-26452    |    Microsoft Windows 6.3.9600    |   Need help?


Thanks you.
6 years ago
Thanks! We'll investigate - https://github.com/nopSolutions/nopCommerce/issues/2662
6 years ago
BUG?

/Admin/Customer/AddressEdit?customerId=1&addressid=1
/Admin/Customer/AddressCreate?customerId=12

These functions are taking me to errorpage.htm.  The active log file has no information that pertains to this error.

$10?
6 years ago
BUG?

On the onepagecheckout page, the FedEx plugin keeps on telling me that the 'FROM country is not specified' even though it is.  This happens whether you use the billing address or try to add a new shipping address.
6 years ago
koray wrote:
BUG?

/Admin/Customer/AddressEdit?customerId=1&addressid=1
/Admin/Customer/AddressCreate?customerId=12

These functions are taking me to errorpage.htm.  The active log file has no information that pertains to this error.

$10?

Yes, the bug. But you're a little bit later =))) It's already fixed  (just 4 hours ago)
6 years ago
koray wrote:
BUG?

On the onepagecheckout page, the FedEx plugin keeps on telling me that the 'FROM country is not specified' even though it is.  This happens whether you use the billing address or try to add a new shipping address.

No. You just haven't configured the origin address in admin area > configurtion > settings > shipping settings (country and zip)
6 years ago
IGNORE - I see that it moved to the marketplace.
----------
What happened to the USPS (Shipping.USPS) plugin?  It does not seem to be included with this version.
6 years ago
Great job, Andrei!
Rewriting nopCommerce in .NET Core was surely a titanic effort, but it's the way to go.

Quick question: is building / running from the command line supposed to work?

Because this is what I get when I run "DOTNET RUN" or "DOTNET BUILD" in the Nop.Web folder:

D:\code\nopCommerce\src\Presentation\Nop.Web> dotnet build
Microsoft (R) Build Engine version 15.4.8.50001 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Nop.Core -> D:\code\nopCommerce\src\Libraries\Nop.Core\bin\Debug\net461\Nop.Core.dll
  Nop.Data -> D:\code\nopCommerce\src\Libraries\Nop.Data\bin\Debug\net461\Nop.Data.dll
  Nop.Services -> D:\code\nopCommerce\src\Libraries\Nop.Services\bin\Debug\net461\Nop.Services.dll
  Nop.Web.Framework -> D:\code\nopCommerce\src\Presentation\Nop.Web.Framework\bin\Debug\net461\Nop.Web.Framework.dll
  Nop.Web -> D:\code\nopCommerce\src\Presentation\Nop.Web\bin\Debug\net461\Nop.Web.exe
D:\code\nopCommerce\src\Build\ClearPluginAssemblies.proj(110,5): error : MSB4801: The task factory "CodeTaskFactory" is not supported on the .NET Core version of MSBuild.
D:\code\nopCommerce\src\Build\ClearPluginAssemblies.proj(110,5): error MSB4036: The "NopClearPluginsPath" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\Program Files\dotnet\sdk\2.0.2" directory.

Build FAILED.

D:\code\nopCommerce\src\Build\ClearPluginAssemblies.proj(110,5): error : MSB4801: The task factory "CodeTaskFactory" is not supported on the .NET Core version of MSBuild.
D:\code\nopCommerce\src\Build\ClearPluginAssemblies.proj(110,5): error MSB4036: The "NopClearPluginsPath" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\Program Files\dotnet\sdk\2.0.2" directory.
    0 Warning(s)
    2 Error(s)

Time Elapsed 00:00:37.92


NOTES:
* I had previously installed the full .NET Core 2.0 SDK
* the site runs normally when launched from VS 2017
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.