Just wanted to note that Deploy.bat will do what Prepare.bat does, with the addition of creating the deployable folder. Prepare was meant for bringing plugins to "Presentation/Nop.Web/Plugins/.." for development purposes. I should probally name them a little different.
Thanks for video. Is there supposed to be sound? (I don't hear any) It is a bit hard to follow without sound. The video is quite grainy. (hard to read)
I don't quite understand - is it necessary to Build in VS, and run Prepare.bat, and Run Deploy.bat? It seems redundant.
I built OK in VS2010, but when I run either batch file, I get..
Build FAILED.
"C:\...\nopCommerce_a51022508a91\build\nop.proj" (Deploy target) (1) -> "C:\...\nopCommerce_a51022508a91\NopCommerce.sln" (default target) (2) -> (ValidateSolutionConfiguration target) -> C:\...\nopCommerce_a51022508a91\NopCommerce.sln.metaproj : error MSB4126: The specified solution configuration "Release|HPD" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration.
Thanks for video. Is there supposed to be sound? (I don't hear any) It is a bit hard to follow without sound. The video is quite grainy. (hard to read)
I don't quite understand - is it necessary to Build in VS, and run Prepare.bat, and Run Deploy.bat? It seems redundant.
I built OK in VS2010, but when I run either batch file, I get..
Build FAILED.
"C:\...\nopCommerce_a51022508a91\build\nop.proj" (Deploy target) (1) -> "C:\...\nopCommerce_a51022508a91\NopCommerce.sln" (default target) (2) -> (ValidateSolutionConfiguration target) -> C:\...\nopCommerce_a51022508a91\NopCommerce.sln.metaproj : error MSB4126: The specified solution configuration "Release|HPD" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration.
You don't have to run bat files. I just changed properties of Web project to point to correct IIS virtual directories, hit Build button, and you can hit F5 to start debugging. Although Admin does still not work now, but I don't think it was build issue.
Thanks for video. Is there supposed to be sound? (I don't hear any) It is a bit hard to follow without sound. The video is quite grainy.
There is no sound. (what you want me to talk about?) there is clear video how to publish nop v2.0 to hosted environment. The grains comes because you need to watch this video in HD
If you have better solution please share with us.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.