Building error (V4 latest changeset )

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
After moving the solution to a new folder, Im getting a building error :

No executable found matching command "dotnet-C:\Websites\Windalert"
5>C:\Websites\Windalert Store\WindalertWeb\src\Build\ClearPluginAssemblies.proj(32,5): error MSB3073: The command "dotnet C:\Websites\Windalert Store\WindalertWeb\src\Build\ClearPluginAssemblies.dll Paths=C:
----- list of all plugins -------" exited with code 1.
5>Done building project "ClearPluginAssemblies.proj" -- FAILED.
6 years ago
I guess its a problem with the ClearPluginAssemblies.proj

anyone?
6 years ago
Yes, this problem in ClearPluginAssemblies.proj. We will fixed it soon, but you can fix it your self: mome your project to the path without spaces, or try to change the line
<Exec Command="dotnet $(MSBuildProjectDirectory)\ClearPluginAssemblies.dll Paths=@(PluginsFolders) FileNames=@(DllFileNames) PluginPath=$(PluginPath) SaveLocalesFolders=$(SaveLocalesFolders)" />
to the
<Exec Command='dotnet "$(MSBuildProjectDirectory)\ClearPluginAssemblies.dll" Paths=@(PluginsFolders) FileNames=@(DllFileNames) PluginPath=$(PluginPath) SaveLocalesFolders=$(SaveLocalesFolders' />
6 years ago
thanks man

that works for me
6 years ago
We fixed this problem. Please see this commit for more details
5 years ago
Dear Support Team,
I ask for urgent help.

How can I solve the following problem?

C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Build\ClearPluginAssemblies.proj(25,2): error MSB3073: The command "dotnet …. exited with code 9009


@To Sergey-K:
Dear Sergey, your proposed solution does not work.

What have I done:
-I have Nop version 410 downloaded also this commit (https://github.com/nopSolutions/nopCommerce)
-NET Core 2.1 installed(http://docs.nopcommerce.com/pages/viewpage.action?pageId=10256757)
-I use VS 2019 community edition

Could you please make a youtube video for it?

Thanks a lot, RS
PS”Can I download a working 410 version somewhere?”

Bug:
C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Build\ClearPluginAssemblies.proj(25,2): error MSB3073: The command "dotnet "C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Build\ClearPluginAssemblies.dll" Paths= FileNames= PluginPath=C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\DiscountRules.CustomerRoles\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\ExchangeRate.EcbExchange\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\ExternalAuth.Facebook\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Payments.CheckMoneyOrder\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Payments.Manual\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Payments.PayPalStandard\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Payments.Square\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Payments.Worldpay\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Pickup.PickupInStore\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Shipping.FixedByWeightByTotal\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Shipping.UPS\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Tax.FixedOrByCountryStateZip\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Widgets.GoogleAnalytics\;C:\Users\rolan\Desktop\Geschaeftlich\l4u_410\nopCommerce_4.10_Source\Presentation\Nop.Web\Plugins\Widgets.NivoSlider\ SaveLocalesFolders=" exited with code 9009
3 years ago
Sergei-k wrote:
We fixed this problem. Please see this commit for more details


I still have the same problem :s
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.